Transparent memory-mapped emulation of I/O calls

ABSTRACT

A virtual-machine-based system provides a mechanism to implement application file I/O operations of protected data by implementing the I/O operations semantics in a shim layer with memory-mapped regions. The semantics of these I/O operations are emulated in a shim layer with memory-mapped regions by using a mapping between a process&#39; address space and a file or shared memory object. Data that is protected from viewing by a guest OS running in a virtual machine may nonetheless be accessed by the process.

RELATED APPLICATIONS

This application claims priority from provisional patent applicationSer. No. 60/983,797, filed 30 Oct. 2007, entitled “AVirtualization-Based Approach To Retrofitting Protection In CommodityOperating Systems,” the entire contents of which is hereby incorporatedby reference herein.

This application is related to:

Ser. No. 12/261,147, entitled “Providing VMM Access to Guest VirtualMemory,” filed on even date herewith, the entire contents of which ishereby incorporated by reference for all purposes;

Ser. No. 12/261,159, entitled “Secure Identification Of ExecutionContexts,” filed on even date herewith, the entire contents of which ishereby incorporated by reference for all purposes;

Ser. No. 12/261,194, entitled “Cryptographic Multi-Shadowing WithIntegrity Verification,” filed on even date herewith, the entirecontents of which is hereby incorporated by reference for all purposes;and

Ser. No. 12/261,623, entitled “Transparent VMM-Assisted User-ModeExecution Control Transfer,” filed on even date herewith, the entirecontents of which is hereby incorporated by reference for all purposes.

FIELD OF THE INVENTION

One or more embodiments of the present invention relate to implementingapplication file I/O operations by emulating the semantics of these I/Ooperations in a shim layer with memory-mapped regions by using a mappingbetween a process' address space and a file or shared memory object.

BACKGROUND OF THE INVENTION

Commodity operating systems (OS) are used in amazingly diverseenvironments, from ubiquitous use in the home, to service in commercial,government, and military settings. These systems are tasked withhandling all manner of sensitive data, from individual passwords andcryptokeys, to databases of social security numbers, to sensitivedocuments, and voice traffic.

The security of known commodity operating systems, however, is less thanideal. While some facets of their security will continue to improve, itis believed that competitive pressures to provide richer functionalityand retain compatibility with existing applications will keep thecomplexity of such systems high and, therefore, their security assurancelow.

Over the years, a variety of techniques has been used for executingmultiple software modules within a computer system, thereby providingsome amount of security. Early computer systems could execute multiplesoftware programs, but they could only execute one program at a time.Such computers might load one program into memory and execute it tocompletion or other termination, before proceeding to a subsequentprogram that would then be loaded into memory and executed. As anotherexample, various multitasking operating systems enable multiple programs(or selected portions thereof) to be loaded into memory at one time andexecuted in an alternating manner, according to a scheduling algorithm.Also, some processors include multithreading capabilities that enablemultiple threads of one or more programs to be executed simultaneouslyon a single processor. Finally, multiprocessor computer systems havealso become commonplace, in which each processor can execute one or morethreads all at the same time.

Many computer systems generally attempt to isolate the code and data ofeach different software module from the code and data of any othersoftware module within the computer system. As a result, one softwaremodule then cannot interfere with the execution of another softwaremodule by altering the latter's code or data. Such isolation may beprovided for code and/or data that is stored on a hard drive (or othersecondary data storage means) and/or that is resident in main memory (orother primary data storage means). The term “data” is generally used ina broad sense, to include data that is operated on by the instructions(code) of a software module as well as the contents of a stack and anyother possible forms of data that are associated with a software module.

As one example of the isolation of code and data, many systems implementa virtual addressing mechanism, in which different software moduleswithin the system have different virtual address spaces, with eachvirtual address space generally being mapped to different portions ofthe physical address space of the computer system, so that the virtualaddresses of a given software module are generally only mapped tophysical addresses that contain the code or data of that particularsoftware module. Virtual addressing mechanisms are well understood byone of ordinary skill in the art. A given software module may attempt toaccess every memory location in its own virtual address space, accessingevery memory location to which it has access, and it will still only beable to access its own code and data (assuming that there is no sharedmemory). Thus, providing a virtual addressing mechanism provides someisolation between the code and data of multiple software modules in acomputer system and, therefore, provides some security.

Various other protection mechanisms may also be implemented in suchcomputer systems to isolate the code and/or data of multiple softwaremodules from one another.

The x86 architecture provides two primary memory protection mechanismsthat may be used by an OS (or other system software) to try to isolatethe code and data of multiple tasks or processes that execute on theprocessor, namely, a segmentation mechanism and a paging mechanism.Windows and Linux use the paging mechanism, but they generally do nottake advantage of the segmentation mechanism. Instead, these OSs definesegments that include the entire addressable range of the processor, sothat the segmentation protection mechanism becomes ineffective inproviding isolation between the code and data of multiple tasks. Thus,for simplicity, this discussion focuses on the paging mechanism of thex86 processor, which implements a virtual addressing mechanism. Theinvention, however, is not limited to implementations using the x86processor, or implementations using similar memory protectionmechanisms.

Generally, for Windows and Linux, different user processes are generallygiven different virtual address spaces. The OS creates a different setof page tables (and a page directory) for each virtual address space,which maps the respective virtual addresses to physical addresses. Thus,the page tables for a given user process map that process's virtualaddresses to the physical addresses that contain the code and data forthat process. The page tables for the user processes also containmappings for code and data of the OS, but the user processes cannot usethese mappings because the user processes are executed at a CurrentPrivilege Level (CPL) of 3 and these mappings are set to require asupervisor, i.e., a higher, privilege level (a CPL of 0, 1 or 2).Otherwise, the page tables for a given user process generally onlycontain mappings to physical memory pages that contain that process'scode and data. Therefore, a user process can generally only access itsown code and data. Executing the user processes at a CPL of 3 alsoprevents the processes from modifying their own page tables. Otherwise,a process could add entries to its page tables that map to any physicaladdress in the system, so that the process could give itself access tothe code and data of other software modules, including other userprocesses and the OS.

Windows and Linux generally provide adequate protection for the softwaremodules in a computer system, so long as all of the software modules arewell designed and well behaved, i.e., they are not attempting tocircumvent the protection mechanism. Thus, many processes may be runningconcurrently in such a computer system, with the OS giving each processa share of the system resources, including processor time, memory spaceand hard disk space, without any of the processes interfering with thecode or data of the other processes.

As shown in FIG. 1, a simple computer system 2A has multiple softwaremodules. The computer system 2A includes system hardware 100A, an OS20A, a first application 40A and a second application 40B. The systemhardware 100A may be conventional hardware based on, for example, thex86 platform, and the OS 20A may be, for example, Windows or Linux. Theapplications 40A and 40B may be any applications designed to run on thesystem hardware 100A and the OS 20A. The OS 20A also includes a set ofdrivers 29A, which may be conventional drivers for the OS 20A, possiblyincluding one or more drivers from a company that is different from theOS vendor (a third party vendor).

The OS 20A, in conjunction with the system hardware 100A, attempts toisolate the code and data of the applications 40A and 40B from oneanother. For example, the OS 20A and the system hardware 100A mayimplement a virtual addressing mechanism, as described above. Asillustrated in FIG. 1, implementing such a protection mechanism may becharacterized as establishing an isolation barrier 80B between theapplications 40A and 40B, preventing (or at least hindering) oneapplication from accessing the code and data of the other application.There may also be some code and/or data that is shared explicitly ortransparently between the applications 40A and 40B. Techniques are knownfor allowing such sharing of code and data, while maintaining isolationbetween the applications 40A and 40B. For example, the OS 20A may markphysical memory pages that contain shared code or data as read only,such as when using a copy-on-write (COW) technique.

The isolation barrier 80B may be referred to as an “OS isolationbarrier” because it is implemented by the OS 20A, in conjunction withthe system hardware 100A. The OS 20A, again in conjunction with thesystem hardware 100A, also establishes an OS isolation barrier 80Abetween the OS 20A and all applications in the system, including theapplications 40A and 40B, so that the applications are prevented (orhindered) from directly accessing the code and data of the OS 20A. Inthe case of a Windows or Linux OS running on an x86 platform, as above,the OS isolation barrier 80A is established by executing theapplications in the system at a CPL of 3 and requiring a supervisorprivilege level to access memory pages containing the code and data ofthe OS 20A.

Although the Windows and Linux OSs provide adequate isolation betweensoftware modules for computer systems that contain only well designedand well behaved software modules, malicious software modules have beenknown to wreak havoc in such computer systems by circumventing theseprotection mechanisms. In particular, such malicious software moduleshave been known to breach the OS isolation barriers 80B and 80A, andcorrupt the code and/or data of other applications in the system, and/orof the OS itself. Numerous security vulnerabilities have been discoveredin the Windows OSs and in the Linux distributions, and many of thesevulnerabilities have been exploited by hackers using different types ofmalicious software, such as viruses, worms, etc. Poorly designed orimplemented software as well as misconfigured, though well-written,software may inadvertently bypass these protection mechanisms too andmay, unintentionally, wreak havoc in a computer system. While thepresent description generally relates to protecting against malicioussoftware, it also applies to protecting against software thatinadvertently has the same or similar effects as intentionally malicioussoftware.

As is too well-known, hackers exploit the vulnerabilities of today'ssystems for a variety of reasons and with a variety of goals, some beingrelatively benign and others being quite destructive or disruptive. Asone example, a malicious software module may be written and deployedthat searches for sensitive data on a computer's hard drive or in itsmemory and transmits any such sensitive data back to the hacker thatlaunched the malicious code.

Security threats and data breaches have been gaining greater notoriety,and it is widely accepted that something should be done to improve thesecurity of the ubiquitous personal computer. In particular, there is arecognized need to improve the security for the vast number of computersbased on the x86 architecture. Many believe that software changes alonewill not provide adequate protection. Accordingly, many differentcompanies are working toward solutions that involve substantial changesto both the system hardware and the system software, i.e., the operatingsystem, of a computer system. Many such security measures, however,require substantial changes to application level software as well.

With respect to the ubiquitous x86 platform, much of the work being donein this area requires substantial hardware changes or an entirely newhardware platform. This work would also require substantial changes toexisting software platforms, including system software and possiblyapplication software. Applications in some of these implementationsmight also have limited access to input/output devices because of alimited supply of trusted device drivers.

The amount of money that is invested in computer hardware and softwarebased on the x86 architecture throughout the world is enormous. Manyindividuals, businesses, schools, governments and other organizationswill be reluctant to scrap their current x86 systems, along with all thesoftware that currently runs on x86 systems, and replace them with newtechnology. Even if a new, more secure and widely accepted hardwareplatform were available today, it would still take a long time for thenew hardware to become anywhere near as widespread as the x86 platformis today. In the meantime, a large number and proportion of computerswould remain vulnerable to the security threats described above.

Notwithstanding the foregoing, there are some proposed security measuresthat may be implemented primarily in software. In particular, there aresome such measures that use virtualization technology to create multiplevirtual machines (VMs), where different software modules run indifferent VMs. It is widely recognized that a well-designed andimplemented virtualization layer can generally provide much greaterisolation between multiple VMs than a general OS can provide betweenmultiple software modules.

A general computer system 2B, referring now to FIG. 2, is described inco-pending application Ser. No. 11/584,178, filed 20 Oct. 2006, titled“Isolating Data within a Computer System Using Private Shadow Mappings,”herein incorporated by reference in its entirety for all purposes, inwhich multiple VMs are implemented to isolate multiple software modulesfrom one another. The computer system 2B includes system hardware 100B,which may be conventional hardware, such as hardware based on the x86platform. The system hardware 100B may be substantially the same as thesystem hardware 100A of FIG. 1, or it may be substantially different.Virtualization software 200A executes on the system hardware 100B andsupports a plurality of VMs, such as a first VM 300A and a second VM300B, in a known manner. Virtualization software 200A may comprise avirtual machine monitor (VMM,) for example, such as a VMM as implementedin a virtualization product of VMware, Inc. of Palo Alto, Calif. Such aVMM and other possible units of the virtualization software 200A aredescribed in greater detail below.

In supporting the VM 300A, the virtualization software 200A virtualizesa virtual system hardware 310A, which may be based on an existinghardware platform, such as the x86 platform. An OS 20B, along with a setof drivers 29B, runs on the virtual system hardware 310A. The OS 20B maybe any OS designed to run on the hardware platform virtualized in thevirtual hardware 310A. For example, if the virtual hardware 310A isbased on the x86 platform, the OS 20B may be, for example, a Windows OS,Solaris OS, Mac OS X, Novell Netware, or a Linux OS. The set of drivers29B may be conventional drivers for the OS 20B. A first application 40Hand a second application 40D run on the OS 20B. The applications 40H and40D may be any applications designed to run on the platform of thevirtual hardware 310A and the OS 20B.

Similar to the OS 20A of FIG. 1, the OS 20B, in conjunction with thevirtual system hardware 310A, attempts to isolate the code and data ofthe applications 40H and 40D from one another, establishing an OSisolation barrier 80B between the applications 40H and 40D. Also similarto the OS 20A of FIG. 1, the OS 20B, again in conjunction with thevirtual system hardware 310A, also establishes an OS isolation barrier80A between the OS 20B and all applications in the VM 300A, includingthe applications 40H and 40D. Thus, the VM 300A may be substantially thesame as the computer system 2A, except that the virtual system hardware310A is virtual hardware, virtualized by the virtualization software200A, instead of physical hardware.

In supporting the VM 300B, the virtualization software 200A virtualizesa virtual system hardware 310B in a like manner as done for the VM 300A.

The virtualization software 200A isolates the VMs in the computer system2B from one another. For example, the virtualization software 200Aallows software within the VM 300A to access portions of physical memoryin the system hardware 100B and it allows software within the VM 300B toaccess other portions of the physical memory. The virtualizationsoftware 200A maps attempted memory accesses from the respective VMs300A and 300B to different portions of the physical memory, ensuringthat no memory address generated by software in one VM can access codeor data of another VM. In a similar manner, the virtualization software200A maps attempted hard disk accesses from the respective VMs 300A and300B to different portions of one or more hard disks in the systemhardware 100B, ensuring that one VM cannot access the hard disk space ofanother VM.

The virtualization software 200A also takes other precautions to isolatethe VMs in the computer system 2B from one another, and from thevirtualization software 200A, itself. For example, U.S. Pat. No.7,281,102 to Agesen et al., “Restricting Memory Access to Protect Datawhen Sharing a Common Address Space”, (“the '102 patent”), describesmethods that may be used to enable a VMM to occupy a portion of a linearaddress space of a VM, while preventing the VM from accessing the memoryof the VMM. There are also various other methods that enablevirtualization software to coexist with VMs in a virtual computersystem, while protecting or isolating the virtualization software fromsoftware within the VMs. The virtualization software 200A may preventsoftware within the VMs 300A and 300B from directly accessing a DirectMemory Access (DMA) device to prevent the possibility that the DMAdevice could be used to access either the hard disk space or the memoryof other VMs or of the virtualization software itself.

Thus, the virtualization software 200A, in conjunction with the systemhardware 100B, may be said to establish a first isolation barrier 280Bbetween the VMs 300A and 300B and a second isolation barrier 280Abetween the virtualization software 200A and all VMs in the computersystem 2B, including the VMs 300A and 300B. The isolation barriers 280Aand 280B may be referred to as “virtualization barriers” because theyare implemented by the virtualization software 200A, in conjunction withthe system hardware 100B. The isolation barriers 280A and 280B may alsobe referred to as virtualization barriers because they are establishedthrough the virtualization of hardware resources, such as thevirtualization of system memory.

Virtualization techniques may provide better security and more effectiveisolation between multiple software modules than a general OS mayprovide. Thus, the virtualization barriers 280A and 280B of FIG. 2 cangenerally provide much better isolation between the multiple VMs 300Aand 300B and the virtualization software 200A than the OS isolationbarriers 80A and 80B of FIG. 1 provide between the multiple applications40A and 40B and the OS 20A. Although computer systems that establishmultiple VMs and that run different software modules within thedifferent VMs generally provide better isolation for the softwaremodules than do general OSs, such virtual computer systems have otherlimitations.

As an example of one limitation, if the software within a VM becomescorrupted by malicious software, the same problems described aboverelative to non-virtualized computer systems can occur within theaffected VM. The software modules within the particular VM may becompromised by the malicious software. Approaches to retrofittingoperating systems to possess higher-assurance security executionenvironments using multiple virtual machines, new operating systems,secure co-processors, or substantial changes to the processorarchitecture have been explored. Unfortunately, these may demand notinsignificant changes in how applications are written and used, and howOS resources are managed. Such departures from standard operation pose asubstantial barrier to adoption of these known approaches.

SUMMARY OF THE INVENTION

In one embodiment of the present invention, in a computer systemcomprising a virtual machine monitor (VMM) running on system hardwareand supporting a virtual machine (VM) having a first application and aguest OS running therein, a method of processing file I/O comprises: afirst shim program configured to intercept any file I/O call from thefirst application; the first shim program emulating file I/O semanticsof any intercepted file I/O call by mapping a target file to which theintercepted file I/O call was directed to a first memory region; and thefirst application accessing a version of the target file from the firstmemory region.

In another embodiment of the present invention, in a computer systemcomprising a virtual machine monitor (VMM) running on system hardwareand supporting a virtual machine (VM) having a first application and aguest OS running therein, a method of accessing a first resource thatcomprises first encrypted resource data comprises: the first applicationissuing a first access request for access to the first resource;intercepting the first access request such that the guest OS does notreceive the first access request; mapping the first resource to a firstmemory region; and the first application accessing unencrypted firstresource data from the first memory region.

In yet another embodiment of the present invention, in a computer systemcomprising a virtual machine monitor (VMM) running on system hardwareand supporting a virtual machine (VM) having a first application and aguest OS running therein, a method of the first application accessing afirst file, wherein the first application accesses an unencryptedversion of the first file, comprises: the first application issuing afirst access request for access to the first file; intercepting thefirst access request such that the guest OS does not receive the firstaccess request; mapping the first file to a first memory region; and thefirst application accessing the unencrypted version of the first filefrom the first memory region.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a computer system running multiple software moduleson a general operating system;

FIG. 2 illustrates a virtual computer system with multiple virtualmachines (VMs) for running multiple software modules;

FIG. 3 illustrates a virtual computer system installed on a hostplatform, with a virtual machine monitor (VMM) at the same system levelas the host operating system;

FIG. 4 illustrates an alternative configuration of a virtual computersystem, which includes a kernel on which is run the VMM of FIG. 3;

FIG. 5 is a representation of components used for known address mappingfunction;

FIG. 6 is a block diagram of the architecture of one embodiment of thepresent invention;

FIG. 7 is a representation of multiple physical address mapping modulesin accordance with one embodiment of the present invention;

FIGS. 8A and 8B represent a flowchart of a process in accordance withone embodiment of the present invention;

FIG. 9 is a state transition diagram for managing cloaked pages inaccordance with one embodiment of the present invention;

FIG. 10 is a representation of the components involved in metadataprotection in accordance with an embodiment of the present invention;

FIG. 11 is a representation of the control flow for handling faults andinterrupts in accordance with an embodiment of the present invention;

FIG. 12 is a state transition diagram for the control flow for handlingsystem calls in accordance with an embodiment of the present invention;and

FIG. 13 is a flowchart of the steps for accessing memory in accordancewith one embodiment of the present invention.

DETAILED DESCRIPTION

Application security is often limited by the poor assurance of commodityoperating systems. A virtual-machine-based system in accordance with anembodiment of the present invention may protect the privacy andintegrity of application data, even in the event of a total OScompromise. Embodiments of the present invention present an applicationwith a normal view of its resources, but the OS with an encrypted viewof those resources. This allows the operating system to carry out thecomplex tasks of managing an application's resources, without allowingit to read or modify them. Thus, embodiments of the present inventionoffer defenses against application data being compromised.

Embodiments of the present invention build on “multi-shadowing,” amechanism that presents different views of “physical” memory, dependingon the context performing the access. This approach offers an additionaldimension of protection beyond the hierarchical protection domainsimplemented by traditional operating systems and processors.

Many embodiments of the present invention do not replace the role of anexisting OS for managing resources. Instead, the isolation capabilitiesof the virtualization layer are extended to allow protection of entitiesinside a virtual machine.

The technique of “multi-shadowing” leverages the extra level ofindirection offered by memory virtualization in a virtual machinemonitor (VMM) to provide a protection layer. Conceptually, as will bedescribed below, a typical VMM maintains a one-to-one mapping from guest“physical” addresses to actual machine addresses. Multi-shadowingreplaces this with a one-to-many, context-dependent mapping, providingmultiple views of guest memory. Embodiments of the present inventionextend multi-shadowing to present an application with a cleartext viewof its pages, and the OS with an encrypted view, a technique referred toas “cloaking.” Encryption-based protection allows resources to remainaccessible to the OS, yet secure, permitting the OS to manage resourceswithout compromising application privacy or integrity.

Multi-Shadowed Cloaking

Prior to the detailed description of embodiments of the presentinvention, the operation of traditional virtualized systems will bebriefly explained, followed by an explanation of how these systems areextended to support multi-shadowing according to embodiments of thepresent invention. The manner in which multi-shadowing is coupled withencryption to implement cloaking, providing both encrypted andunencrypted views of memory is then discussed.

Discussion of Virtualization

As is well known in the art, a virtual machine (VM) is a softwareabstraction, i.e., a “virtualization” of an actual or an abstractphysical computer system. The VM runs as a “guest” on an underlying“host” hardware platform. Guest software, such as a guest OS and guestapplications, may be loaded onto the virtual computer for execution. Theguest OS may, but need not be, the same as the OS or other systemsoftware running at the system level in the host. For example, a WindowsOS may run in the VM even though the OS used to handle actual I/O(input/output), memory management, etc., on the host might be a LinuxOS. As long as a suitable interface is provided between the VM and thehost platform, a user of a VM need not even be aware that she is notusing a “real” computer, that is, a system with hardware dedicatedexclusively to her use. The existence of the underlying host can be madetransparent to a user of the VM and to the guest software itself.

A Hosted Virtual Computer System

FIG. 3 illustrates the main components of a computer system 2X thatsupports a VM 300X, as generally implemented in the Workstationvirtualization product of VMware, Inc. As in conventional(non-virtualized) computer systems, both system hardware 100X and systemsoftware 19W are included. The system hardware 100X includes CPU(s)112X, which may be a single processor, or two or more cooperatingprocessors in a known multiprocessor arrangement. The system hardwarealso includes system memory 118X, one or more disks 120X, and some formof Memory Management Unit (MMU) 116X. One of ordinary skill in the artwill understand that the system may not contain any disks. In otherwords, the system may instead use network-attached storage (NAS), suchas a remote file server, i.e., one using NFS (Network File System) orCIFS (Common Internet File System) protocols, or a remote storage arrayvia a storage-area network (SAN), or via a standard network, e.g., usingthe iSCSI (Internet Small Computer System Interface) protocol. Further,flash memory could be used to replace the disks. As is understood in thefield of computer engineering, the system hardware also includes, or isconnected to, conventional registers, interrupt handling circuitry, aclock, etc., which, for the sake of simplicity, are not shown in thefigure.

The system software 19W either is or at least includes an operatingsystem 20W, which has drivers 29W as needed for controlling andcommunicating with various devices 123X, and usually with the disk 120Xas well. Conventional applications 40W, if included, may be installed torun on the hardware 100X via the system software 19W and any driversneeded to enable communication with those devices.

The virtual machine (VM) 300X—also known as a “virtual computer”—is asoftware implementation of a complete computer system. In the VM, thephysical system components of a “real” computer are emulated insoftware, that is, they are virtualized. Thus, the VM 300X willtypically include virtualized (“guest”) system hardware 310X, which inturn includes one or more virtual CPUs 312X (VCPU), virtual systemmemory 318X (VMEM), one or more virtual disks 320X (VDISK), and one ormore virtual devices 323X (VDEVICE), all of which are implemented insoftware using known techniques to emulate the corresponding componentsof an actual computer. It should be noted, however, that a VDISK and aVDEVICE are typically included but are not strictly necessary. Theconcept, design and operation of virtual machines are well known in thefield of computer science.

The VM 300X also includes system software 19X, which may include a guestoperating system 20X, which may, but need not, simply be a copy of aconventional, commodity OS, as well as drivers 29X as needed, forexample, to control the virtual device(s) 323X. Note that a disk—virtualor physical—is also a “device,” but is usually considered separatelybecause of its essential role. Of course, most computers are intended torun various applications, and a VM is usually no exception.Consequently, by way of example, FIG. 3 illustrates one or moreapplications 40X installed to run on the guest OS 20X; any number ofapplications, including none at all, may be loaded for running on theguest OS, limited only by the requirements of the VM. Software runningin the VM 300X, including the guest OS 20X and the guest applications40X, is generally referred to as “guest software.”

Note that although the virtual hardware “layer” 310X will be a softwareabstraction of physical components, the VM's system software 19X may bethe same as would be loaded into a hardware computer. The modifier“guest” is used here to indicate that the VM, although it acts as a“real” computer from the perspective of a user and guest software, isactually just computer code that is executed on the underlying “host”hardware and software platform 100X, 19W. Thus, for example, I/O to avirtual device 323X will actually be carried out by I/O to acorresponding hardware device 123X, but in a manner transparent to theVM.

Some interface is usually required between the VM 300X and theunderlying “host” hardware 100X, which is responsible for actuallyexecuting VM related instructions and transferring data to and from theactual, physical memory 118X and other system hardware 100X. Theinterface between the VM and the underlying host system is oftenreferred to as a Virtual Machine Monitor (VMM). As used in this patent,the term VMM should not be interpreted as being limited in any way to orby existing virtualization software that is referred to as a VMM.Instead, the term VMM should be interpreted broadly as virtualizationsoftware that supports the operation of a virtual machine, whether suchvirtualization software is referred to as a VMM, a hypervisor, or ifsome other terminology is used; or, in the event that somevirtualization functionality is implemented or supported in hardware,the term VMM may be interpreted broadly as virtualization logic thatsupports the operation of a virtual machine.

A VMM is usually a relatively thin layer of software that runs directlyon top of a host, such as the system software 19W, or directly on thehardware, and virtualizes the resources of the hardware platform. FIG. 3shows virtualization software 200X, which may be implemented as a VMM,running directly on the system hardware 100X. The virtualizationsoftware 200X is also referred to as a VMM 200X herein, although it mayalternatively comprise other virtualization software that may not beconsidered or called a VMM. The VMM 200X will typically include at leastone device emulator 254X, which may also form the implementation of thevirtual device(s) 323X. The interface exported to the respective VM isusually such that the guest OS 20X cannot determine the presence of theVMM. The VMM also usually tracks and either forwards (to the host OS20W) or itself schedules and handles all requests by its VM for machineresources, as well as various faults and interrupts. FIG. 3 thereforeillustrates an interrupt (including fault) handler 252X within the VMM.The VMM also includes a memory manager 256X. The general features ofVMMs are well known and are therefore not discussed in further detailhere.

A single VM 300X is illustrated in FIG. 3 merely for the sake ofsimplicity; in many installations, there will be more than one VMinstalled to run on the common hardware platform; all may haveessentially the same general structure, although the individualcomponents need not be identical. Also, as shown in FIG. 3, a single VMM200X is the interface for the single VM 300X. It would also be possibleto include the VMM as part of its respective VM. Although the VMM isusually completely transparent to the VM, the VM and VMM may be viewedas a single module that virtualizes a computer system. The VM and VMMare shown as separate software entities in the figures merely for thesake of clarity. Moreover, it would also be possible to use a single VMMto act as the interface for more than one VM.

In the system illustrated in FIG. 3, both the host OS and the VMM areinstalled at system level, meaning that they each run at the greatestprivilege level and can therefore independently modify the state of thehardware processor(s). For I/O to at least some devices, however, theVMM may issue requests via the host OS 20W. To make this possible, aspecial driver VMDRV 290 is installed just as any other driver withinthe host OS 20W is installed and exposes a standard API to a user-levelapplication VMAPP 292. When the system is in the VMM context, meaningthat the VMM is taking exceptions, handling interrupts, etc., but theVMM wishes to use the existing I/O facilities of the host OS, the VMMcalls the driver VMDRV 290, which then issues calls to the applicationVMAPP 292, which then carries out the I/O request by calling theappropriate routine in the host OS.

A line 280X symbolizes the boundary between the virtualized (VM/VMM) andnon-virtualized (host software) “worlds” or “contexts.” The driver VMDRV290 and application VMAPP 292 thus enable communication between theworlds. The boundary 280X may also be characterized as a “virtualizationbarrier”, as that term is used above. The virtualization barrier 280X,however, does not provide as complete a barrier, or as secure a barrier,between the host OS 20W and the VM 300X as the virtualization barrier280B provides between the VM 300A and the VM 300B shown in FIG. 2. Thisis primarily because the system software 19W has direct access to thesystem hardware 100X, including all of the memory 118X and the disk120X, including, in particular, the memory and disk space that containsthe code and data of the VMM 200X and the VM 300X. Accordingly, thevirtualization barrier 280X may be referred to more specifically as a“limited virtualization barrier,” while the virtualization barrier 280Bmay be referred to more specifically as a “complete virtualizationbarrier” or as a “bidirectional virtualization barrier.” Anothervirtualization barrier would be established between the VM 300X and anyother VM in the computer system 2X, although no such othervirtualization barrier is illustrated in FIG. 3 because only one VM isillustrated. A virtualization barrier 280W between the VM 300X and theVMM 200X operates substantially the same as the virtualization barrier280A shown in FIG. 2.

A Kernel-Based Virtual Computer System

In the computer system 2X of FIG. 3, the VMM is co-resident at systemlevel with a host operating system. Both the VMM and the host OS canindependently modify the state of the host processor, but the VMM callsinto the host OS via a driver and a dedicated user-level application tohave the host OS perform certain I/O operations on behalf of the VM. Thevirtual computer in this configuration is thus fully hosted in that itruns on an existing host hardware platform and together with an existinghost OS.

In other implementations, a dedicated kernel, takes the place, andperforms the conventional functions, of the host OS, and virtualcomputers run on the kernel. A “kernel-based” virtual computer system,in which a kernel serves as the system software for one or more VMM/VMpairs, is illustrated in FIG. 4. Compared with a system in which VMMsrun on a host OS, use of a kernel offers greater modularity andfacilitates provision of services that extend across multiple VMs (forexample, for resource management). Compared with the hosted deploymentdescribed above, a kernel may offer greater performance because it canbe co-developed with the VMM and be optimized for the characteristics ofa workload consisting of VMMs. The ESX Server virtualization product ofVMware, Inc., has such a configuration. A kernel-based virtualizationsystem of the type illustrated in FIG. 4 is described in U.S. Pat. No.6,961,941 to Nelson et al., “Computer Configuration for ResourceManagement in Systems Including a Virtual Machine”, (“the '941 patent”).

As shown in FIG. 4, the general configuration of a kernel-based virtualcomputer system 2Y, includes one or more virtual machines (VMs), such asa first VM 300Y and a second VM 300Z, each of which is installed as a“guest” on a “host” hardware platform 100Y. The hardware platform 100Yincludes one or more processors (CPUs) 112Y, system memory 118Y, and oneor more disks 120Y. The hardware 100Y may also include otherconventional mechanisms such as a Memory Management Unit (MMU) 116Y andvarious devices 123Y.

The VM 300Y includes virtual system hardware 310Y, which typicallyincludes at least one virtual CPU 312Y, at least one virtual disk 320Y,a virtual system memory 318Y, and various virtual devices 323Y. The VM300Y also includes a guest operating system 20Y (which may simply be acopy of a conventional operating system) running on the virtual systemhardware 310Y, along with a set of drivers 29Y for accessing the virtualdevices 323Y and the virtual disk 320Y. One or more applications 40Y mayexecute in the VM 300Y on the guest OS 20Y and the virtual systemhardware 310Y. All of the components of the VM may be implemented insoftware using known techniques to emulate the corresponding componentsof an actual computer. This implementation of the VM 300Y may generallybe substantially the same as the implementation of the VM 300X shown inFIG. 3.

The VMs 300Y and 300Z are supported by a virtualization software 200Ycomprising a kernel 202Y and a set of VMMs, including a first VMM 250Yand a second VMM 250Z. In this implementation, each VMM supports one VM.Thus, the VMM 250Y supports the VM 300Y and the VMM 250Z supports the VM300Z. The VMM 250Y includes, among other components, device emulators254Y, which may constitute the virtual devices 323Y that the VM 300Yaccesses. The VMM 250Y may also include a memory manager 256Y. The VMMalso usually tracks and either forwards (to some form of systemsoftware,) or itself schedules and handles, all requests by its VM formachine resources, as well as various faults and interrupts. A mechanismknown in the art as an exception or interrupt handler 252Y may thereforebe included in the VMM.

The computer system 2Y may, initially, have an existing operating system20Z that may be at system level, and the kernel 202Y may not yet even beoperational within the system. The initial system level interfacebetween the OS 20Z and the system hardware 100Y is represented by adashed line in FIG. 4. In such a case, one of the functions of the OS20Z may be to make it possible to load the kernel 202Y, after which thekernel runs on the native hardware 100Y and manages system resources. Ineffect, the kernel, once loaded, displaces the OS 20Z. Thus, the kernel202Y may be viewed either as displacing the OS 20Z from the system leveland taking this place itself, or as residing at a “sub-system level.”When interposed between the OS 20Z and the hardware 100Y, the kernel202Y essentially turns the OS 20Z into an “application,” which hasaccess to system resources only when allowed by the kernel 202Y. Thekernel then schedules the OS 20Z as if it were any other component thatneeds to use system resources. Accordingly, another interface is shownbetween the OS 20Z and the kernel 202Y for enabling the OS 20Z to accessthe system hardware 100Y. This second interface is shown with a solidline in FIG. 4.

The OS 20Z may also be included to allow applications unrelated tovirtualization to run; for example, a system administrator may need suchapplications to monitor the hardware 100Y or to perform otheradministrative routines. The OS 20Z may thus be viewed as a “console” OS(COS). In such implementations, the kernel 202Y may also include aremote procedure call (RPC) mechanism to enable communication between,for example, the VMM 250Y and any applications 40Z installed to run onthe COS 20Z.

As described in the '941 patent, the kernel 202Y handles the variousVMM/VMs and the COS 20Z as entities that can be separately scheduled,which are referred to as “worlds.” The worlds are controlled by a worldmanager, represented in FIG. 4 within the kernel 202Y as module 212Y.The kernel 202Y may also include an interrupt/exception handler 214Ythat is able to intercept and handle interrupts and exceptions for alldevices on the machine.

The kernel 202Y includes a system memory manager 210Y that manages allmachine memory that is not allocated exclusively to the COS 20Z. Whenthe kernel 202Y is loaded, the information about the maximum amount ofmemory available on the machine is available to the kernel, as well asinformation about how much of it is being used by the COS. Part of themachine memory is used for the kernel 202Y itself and the rest is usedfor the virtual machine worlds. Virtual machine worlds use machinememory for two purposes. First, memory is used to back portions of eachworld's memory region, that is, to store code, data, stacks, etc. Forexample, the code and data for the VMM 250Y is backed by machine memoryallocated by the kernel 202Y. Second, memory is used for the guestmemory of the virtual machine. The memory manager may include anyalgorithms for dynamically allocating or deallocating memory among thedifferent VMs.

The kernel 202Y is responsible for providing access to all devices onthe physical machine. In addition to other modules that the designer maychoose to load onto the system for access by the kernel, the kernel willtypically load conventional drivers as needed to control access todevices. Accordingly, a module 240Y containing loadable kernel modulesand drivers is shown in FIG. 4. The kernel 202Y may interface with theloadable modules and drivers in a conventional manner, i.e., using anAPI or similar interface.

A first virtualization barrier 280V between the COS 20Z and the VMs 300Yand 300Z, a second virtualization barrier 280Y between the VMs 300Y and300Z, and a third virtualization barrier 280Z between the virtualizationsoftware 200Y and the VMs 300Y and 300Z, as well as the COS 20Z, arerepresented in FIG. 4. There would also be additional virtualizationbarriers between any other VMs in the computer system. Thevirtualization barriers 280V and 280Y may be substantially the same asthe virtualization barrier 280B of FIG. 2, while the virtualizationbarrier 280Z may be substantially the same as the virtualization barrier280A.

Overview of Memory Mapping in Virtual Computer Systems

When memory addresses are generated in the VM 300X of FIG. 3, either bythe applications 40X or the guest system software 19X, the addresses aregenerally mapped to corresponding addresses in the physical memory 118X.Both the guest OS 20X and the memory manager 256X are involved in thismapping process. Similarly, when memory addresses are generated in theVM 300Y of FIG. 4, either by the applications 40Y or the system softwareof the VM 300Y, the guest OS 20Y and the memory manager 256Y areinvolved in the process of mapping the addresses to correspondingaddresses in the physical memory 118Y. These address mapping processesare substantially similar in both the hosted virtual computer system 2Xof FIG. 3 and the kernel-based virtual computer system 2Y of FIG. 4.Thus, the following description is generally limited to the process ofmapping addresses from the VM 300X of FIG. 3 to the physical memory118X, although it generally also applies to the corresponding process ofFIG. 4, and to corresponding processes in other virtual computersystems.

Most modern computers implement a “virtual memory” mechanism, asdescribed briefly above, that allows user-level software to specifymemory locations using a set of virtual addresses. These virtualaddresses are then translated or mapped into a different set of physicaladdresses that are actually applied to physical memory to access thedesired memory locations. The range of possible virtual addresses thatmay be used by user-level software constitutes a virtual address space,while the range of possible physical addresses that may be specifiedconstitutes a physical address space. The virtual address space istypically divided into a number of virtual memory pages, each having adifferent virtual page number, while the physical address space istypically divided into a number of physical memory pages, each having adifferent physical page number. A memory “page” in either the virtualaddress space or the physical address space typically comprises aparticular number of memory locations, for example, such as either afour kilobyte (KB) memory page or a two megabyte (MB) memory page in anx86 computer system.

The operation of a virtual memory system is well understood by those ofordinary skill in the art and will not be described in further detailherein. For more information, see “Computer Organization & Design: theHardware/Software Interface,” by David A. Patterson and John L.Hennessy, 2nd ed., Morgan Kaufmann Publishers Inc., San Francisco,Calif., 1998.

Classical Memory Virtualization

Conventional non-virtualized operating systems use page tables to mapvirtual addresses to physical addresses with page granularity. A virtualpage number (VPN) is mapped to a physical page number (PPN), andVPN-to-PPN translations are cached by a hardware translation lookasidebuffer (TLB.)

The classical virtual machine monitor (VMM) provides each virtualmachine (VM) with the “illusion” of being a dedicated physical machinethat is fully protected and isolated from other virtual machines. Tosupport this illusion, physical memory is virtualized by adding an extralevel of address translation. The terms “machine address” and “machinepage number” (MPN) are herein used to refer to actual hardware memory.In contrast, “physical” memory is a software abstraction that presentsthe illusion of hardware memory to a VM. Address translation performedby a guest operating system in a VM maps a guest virtual page number(GVPN) to a guest physical page number (GPPN). The VMM maintains a pmapdata structure for each VM to store GPPN-to-MPN translations. The VMMalso typically manages separate shadow page tables, which containGVPN-to-MPN mappings, and keeps them consistent with the GVPN-to-GPPNmappings managed by the guest OS. As the hardware TLB caches directGVPN-to-MPN mappings, ordinary memory references execute withoutincurring virtualization overhead. It should be noted that the memory118X (FIG. 3) and the memory 118Y (FIG. 4) can also be referred to as“machine” memory. Where necessary, “machine” is used when needed toavoid confusion between “guest physical” and “physical,” as used in avirtual environment.

Referring now to FIG. 5, some of the functional units involved in theaddress mapping process described above will be described. The virtualcomputer system shown in FIG. 5 is a more abstract depiction that canrepresent either of computer systems 2X, 2Y of FIGS. 3, 4, respectively.System hardware 100C includes an MMU 116C, which further includes a TLB117C. It should be noted that elements with reference labels similar tothose shown in FIGS. 3 and 4 have similar, if not the same,functionality.

Virtualization software 200B executes on the system hardware 100C, andmay be substantially the same as the virtualization software 200X ofFIG. 3 or the virtualization software 200Y of FIG. 4. The virtualizationsoftware 200B includes a memory manager 256B, part of the VMM (notshown), which further includes an address mapping module 220B and a setof shadow page tables 222B.

The virtualization software 200B supports a VM 300C that includesvirtual system hardware 310C, which further includes an MMU 316C, whichmay further include a virtual TLB (VTLB) 317C, although the MMU 316C mayalso be implemented without a virtual TLB. The VM 300C also includes aguest OS 20D and a set of one or more applications 40G. The guest OS 20Dincludes a set of guest OS page tables 22D.

The guest OS 20D generates the guest OS page tables 22D that map theguest software virtual address space to what the guest OS perceives tobe the machine address space. In other words, the guest OS 20D mapsGVPNs to GPPNs. Suppose, for example, that a guest application 40Gattempts to access a memory location having a first GVPN, and that theguest OS has specified in the guest OS page tables that the first GVPNis backed by what it believes to be a machine memory page having a firstGPPN.

The address mapping module 220B keeps track of mappings between theGPPNs of the guest OS 20D and the “real” machine memory pages of themachine memory within the system hardware 100C. Thus, the addressmapping module 220B maps GPPNs from the guest OS 20D to correspondingMPNs in the machine memory. Continuing the above example, the addressmapping module translates the first GPPN into a corresponding first MPN.

The memory manager 256B creates a set of shadow page tables 222B thatare used by the MMU 116C. The shadow page tables 222B include a numberof shadow page table entries (PTEs) that generally correspond to thePTEs in the guest OS page tables 22D, but the shadow PTEs map guestsoftware virtual addresses to corresponding machine addresses in theactual machine memory, instead of to the physical addresses specified bythe guest OS 20D. In other words, while the guest OS page tables 22Dprovide mappings from GVPNs to GPPNs, the shadow PTEs in the shadow pagetables 222B provide mappings from GVPNs to corresponding MPNs. Thus,continuing the above example, instead of containing a mapping from thefirst GVPN to the first GPPN, the shadow page tables 222B would containa shadow PTE that maps the first GVPN to the first MPN. When the guestapplication attempts to access a memory location having the first GVPN,the MMU 116C loads the mapping from the first GVPN to the first MPN inthe shadow page tables 222B into the physical TLB 117C, if the mappingis not already there. This mapping from the TLB 117C is then used toaccess the corresponding memory location in the machine memory pagehaving the first MPN.

Embodiments of the present invention use cloaking to protect unmodifiedlegacy applications running on unmodified commodity operating systems.Cloaking is a low-level primitive that operates on basic memory pages.Nearly all higher-level application resources, including code, data,files, and even Inter-Process Communication (IPC) streams, however, arealready managed as memory-mapped objects by modern operating systems, orcan be adapted as such. As a result, cloaking is sufficiently general toprotect all of an application's major resources.

To implement cloaking some modifications to the normal executionenvironment are provided.

As will be described below in more detail, embodiments of the presentinvention introduce, at load time, a shim program into the address spaceof each cloaked application, mediating all communication with the OS.With assistance from the VMM, the shim interposes on events such assystem calls and signal delivery, modifying their semantics to enablesafe resource sharing between a cloaked application and an untrusted OS.In addition, the shim manages a mapping of guest virtual addresses to“physical resources,” i.e., allocated memory that can be eitherfile-backed or not.

An overview of the architecture of embodiments of the present inventionis presented in FIG. 6. For ease of explanation, a single VM 300 isdepicted, consisting of a guest OS 20 together with multipleapplications 40, one of which is a cloaked application 40C. A VMM 250effectuates a cloaking virtualization barrier 280C between the cloakedapplication 40C and the guest OS 20, similar to the barrier 280 the VMM250 enforces between the guest OS 20 and host hardware 100. A cloakedshim program 600 is provided into the address space of the cloakedapplication 40C. The cloaked shim 600 cooperates with the VMM 250 tointerpose on all control flow between the cloaked application 40C andthe guest OS 20. Additionally, an uncloaked shim 610 is provided andincludes buffer space 612 to provide a neutral area for the guest OS 20and cloaked application 40C to exchange uncloaked data, as will beexplained in more detail below.

Multi-Shadowing

As discussed above, existing virtualization systems present a singleview of guest “physical” memory, generally faithfully emulating theproperties of real hardware. One-to-one GPPN-to-MPN mappings aretypically employed, backing each guest physical page with a distinctmachine page. Some systems implement many-to-one mappings to supportshared memory, e.g., transparent page sharing maps multiple GPPNs, usingcopy-on-write, to a single MPN. However, existing virtualization systemsdo not provide flexible support for mapping a single GPPN to multipleMPNs.

Multi-shadowing, in accordance with embodiments of the presentinvention, is a mechanism that supports context-dependent, one-to-manyGPPN-to-MPN mappings. Conceptually, multiple shadow page tables are usedto provide different views of guest physical memory to different shadowcontexts. The “context” that determines which view (shadow page table)to use for a particular memory access can be defined in terms of anystate accessible to the VMM, such as the current protection ring, pagetable, instruction pointer, contents of a register, contents of a memorylocation, or some other criteria. FIG. 7 shows multiple physical addressmapping modules 500, 500′, 500″ that correspond with the multiple shadowpage tables, with the address mapping modules providing GPPN-to-MPNmappings and the shadow page tables providing corresponding GVPN-to-MPNmappings. Thus, in FIG. 7, a multi-shadow address mapping module 500would have multiple entries having a context portion 502 identifyingCONTEXT1 and multiple mapping portions 504-1, 504-2, 504-3. In theexample shown in FIG. 7, a first guest physical page (GPPN1) is mappedto a first machine page MPN1 for CONTEXT1 but is mapped to a differentmachine page MPN4 for CONTEXT2 as shown in multi-shadow address mappingmodule 500′. Similarly, in a first multi-shadow page table (not shown)for CONTEXT1, corresponding to the address mapping module 500, the GVPNthat maps to GPPN1 would be mapped to MPN1, and, in a secondmulti-shadow page table (not shown) for CONTEXT2, corresponding to theaddress mapping module 500′, the GVPN that maps to GPPN1 would be mappedto MPN4. In an x86 architecture, an MMU walks page tables in hardware,therefore multiple separate page tables—generally one for eachcontext—are implemented.

Traditional operating systems and processor architectures implementhierarchical protection domains, such as protection rings.Multi-shadowing offers an additional dimension of protection orthogonalto existing hierarchies, enabling a wide range of unconventionalprotection policies.

As will be described in more detail below, embodiments of the presentinvention allow a guest OS to perform the tasks of application memorymanagement, without allowing the guest OS to observe the actual memorycontents.

Multi-shadowing ensures that the guest OS or other processes cannot viewcloaked code and data in plaintext. To allow the guest kernel to easilymanage the underlying memory resources, coordination is provided when,for instance, the kernel needs to swap out memory occupied by thecloaked data to disk, as well as for other operations related to cloakedmemory and files. Advantageously, some embodiments of the presentinvention do not rely on the guest kernel using virtual DMA or othermechanisms that can be tracked by the VMM to perform swap and file I/Ooperations. If the kernel did not use DMA to implement these operations,without the advantages of some embodiments of the present invention, itwould be difficult and expensive to track cloaked data using existinghardware and software techniques.

It has been recognized that encryption alone does not prevent the guestkernel from modifying cloaked page contents. Accordingly, someembodiments of the present invention include integrity verification, asdescribed below. The kernel can corrupt application memory by modifyingrandom bits of any cloaked memory page, and any such corrupted data maybe detected before the application attempts to use it. Without integrityverification, an application could behave unexpectedly if using changeddata, possibly leading to compromises that exploit such unexpectedexecution of the program to leak cloaked data.

Memory Cloaking

Cloaking combines multi-shadowing with encryption, presenting differentviews of memory—plaintext and encrypted—to different guest contexts.

Some embodiments of the present invention that implementvirtualization-based cloaking do not require any changes to theprocessor architecture, OS, or applications. Cloaking based onmulti-shadowing represents a relatively small change to the core MMUfunctionality already implemented by a VMM. As an overview, cloakingwill be described using a high-level model. Metadata management andintegration with existing systems are presented below.

Single Page, Encrypted/Unencrypted Views

In accordance with the teachings of some embodiments of the presentinvention, each GPPN uses only a single MPN, and dynamically encryptsand decrypts its contents depending on the context currently accessingthe page. This works well because few pages are accessed simultaneouslyby both the application and the kernel in practice. As an alternateembodiment, two read-only copies of the page could be maintained, oneencrypted, and one plaintext, for pages that are read concurrently fromboth contexts.

When a cloaked page is accessed from outside the shadow context to whichit belongs, the VMM first encrypts the page, using a fresh,randomly-generated initialization vector (IV), then takes a secure hash(H) of this ciphertext. An initialization vector is commonly used incryptography so that two chunks of data, e.g., two pages with the samecontents, do not each encrypt to the same ciphertext. As an example, iftwo identical pages are encrypted, and an IV is not used—then each willencrypt to the same ciphertext, and an attacker will know that the twoencrypted pages have the same contents. This information can be used tomount a “known plaintext” attack. Using a randomly-generated IV, the IVis appended to (or XOR'd with, or combined in some way with) theplaintext before it is encrypted. As identical pages will have differentIVs, each will encrypt to a different ciphertext, assuming that the sameencryption key is used.

The pair (IV, H) is stored securely for future use. During decryption,the correct hash is first verified. If verification fails, theapplication may be terminated. If it succeeds, the cloaked page isdecrypted, and execution proceeds as normal. By checking the hash beforedecryption, any attempts to corrupt cloaked pages will be detected.

In general, referring now to FIGS. 8A and 8B, a method 400 in accordancewith one embodiment of the present invention is presented. Initially, atstep 402, a request for access to a cloaked page (CP) is received, e.g.,through an attempted memory access. Subsequently, step 403, it isdetermined if the CP is plaintext or encrypted. If plaintext, controlpasses to step 404, where it is determined whether or not the requesterbelongs to the shadow context for the CP. If the requester does belongto the shadow context, control passes to step 406 where the CP is mappedinto the requester's shadow mapping. If, on the other hand, therequester is not a member of the shadow context for the requested CP,control passes to step 405 where the page is unmapped from theapplication shadow. An initialization vector (IV) is randomly generated,step 408, and the CP is encrypted using the IV, step 410, to create aciphertext. A hash value (H) is generated for this ciphertext, step 412.The (IV, H) pair is securely stored to correspond with the CP, step 414.In step 416, the ciphertext is mapped into the requester's shadowmapping.

Returning to step 403, if CP is encrypted, control passes to step 418where it is determined whether or not the requester belongs to theshadow context for the CP. If the requester does not belong to theshadow context, control passes to step 420 where the CP is mapped intothe requester's shadow mapping.

If the requester is a member of the shadow context for the requested CP,control passes to step 422 where the (IV,H) pair corresponding to the CPis retrieved. A new hash (NH) value is calculated for the CP, step 424,and compared to the hash H in the retrieved (IV,H) pair, step 426. If NHis not the same as H, control passes to step 428 where a fault conditionis asserted. If NH is the same as H, then CP is decrypted using IV, step430, and decrypted CP is mapped into the requestor's shadow mapping,step 432.

In one embodiment of the present invention a single secret key K_(VMM)managed by the VMM is used to encrypt all pages, as will be describedbelow in more detail. In one embodiment, the encryption uses AES-128(Advanced Encryption Standard) in CBC (Cipher-Block Chaining) mode, andhashing uses SHA-256 (Secure Hash Algorithm); both are standardconstructions. Of course, one of ordinary skill in the art willunderstand that a mode using multiple keys could be supported.

An alternate embodiment of the present invention implements anintegrity-only mode of operation. In this embodiment, the concern is notabout the privacy of the data, so the application data is in plaintext,i.e., not encrypted. As a result, the IV, which is used forencryption/decryption, as above, is not needed.

In “integrity only” mode, the focus is on only detecting tampering, andthus should need only the secure hash. As an alternative implementationto a secure hash H, other cryptographic authentication methods could beused, e.g., a message authentication code (MAC), as known to those ofskill in the art. In any case, a secure hash H or MAC is used to protectthe integrity of encrypted page contents; if a cloaked page iscorrupted, its MAC will change, therefore allowing the modification tobe detected.

Basic Cloaking Protocol

Consider a single guest “physical” page (GPPN). At any point in time,the page is mapped into only one shadow page table—either a protectedapplication shadow used by a cloaked user-space process, or the systemshadow used for all other accesses. When the page is mapped into theapplication shadow, its contents are ordinary plaintext, and applicationreads and writes proceed normally.

FIG. 9 presents a state transition diagram 450 for managing, i.e.,maintaining, the secrecy and integrity of a single cloaked page. Ofcourse one of ordinary skill in the art would understand how to applythis to multiple cloaked pages. Application reads R_(A) and writes W_(A)manipulate plaintext page contents while kernel reads R_(K) and writesW_(K) use an encrypted version of the page. The secure hash H iscomputed and stored immediately after page encryption and verifiedimmediately prior to page decryption.

When the cloaked page is accessed (R_(K), W_(K)) via the system shadowtransition 1, the VMM unmaps the page from the application shadow,encrypts the page, generates an integrity hash, and maps the page intothe system shadow. The kernel may then read the encrypted contents,e.g., to swap the page to disk, and may also overwrite its contents,e.g., to swap in a previously-encrypted page.

When the encrypted page is subsequently accessed (R_(A) W_(A)) via theapplication shadow transitions 2 or 3, the VMM unmaps the page from thesystem shadow, verifies its integrity hash, decrypts the page, and mapsthe page into the application shadow. For an application read R_(A)transition 3, the page is mapped read-only and its (IV, H) pair isretained. If the page is later written W_(A) by the application,transition 4, the (IV, H) pair is discarded, and the page becomesreadable and writable. If the page is instead accessed (R_(K),W_(K)) bythe kernel, transition 5, the VMM proceeds as in transition 1, exceptthat the hash H for the (unmodified) page is not recomputed. Returningto transition 2, for an application write W_(A), the (IV, H) pair isdiscarded as in transition 4, and the page remains readable andwritable.

The read-only plaintext state, where the (IV, H) pair is retained, isgenerally required to correctly handle the case where the kernellegitimately caches a copy of the encrypted page contents. For example,consider the case where the kernel swaps a cloaked page to disk, whichis later paged in due to an application read, and then swapped out againbefore the application modifies it. The kernel can optimize the secondpage-out by noticing that the page is not dirty, and simply unmap thepage without reading it because the on-disk swapped copy would still bevalid. If the (IV, H) pair has been discarded, it would not be possibleto decrypt the page after it is swapped back in.

Cloaking is compatible with copy-on-write (COW) sharing of identicalpages, i.e., those with identical contents, such as described in U.S.Pat. No. 6,789,156 to Waldspurger, “Content-Based, Transparent Sharingof Memory Units” (“the '156 patent”). At the VMM level, a plaintext MPNcan be shared transparently between VMs or within a single VM. Plaintextpages can be shared transparently, and page encryption is handled like aCOW fault. When a cloaked GPPN transitions to an encrypted state, it istreated like a COW fault, and a private MPN is allocated to store theencrypted version of the GPPN.

Virtual DMA

Cloaking is also compatible with virtual devices that access guestmemory using DMA. For example, suppose the guest kernel performs diskI/O on a cloaked memory page via a virtual SCSI adapter. For a diskread, the cloaked page contents are already encrypted on disk, and theVMM simply permits the kernel to issue a DMA request to read the page.

For a disk write, the action taken by the VMM depends on the currentstate of the cloaked page. If the page is already encrypted, the VMMallows the DMA to be performed directly. When the page is in theplaintext read-only state, the VMM first encrypts the page contents withits existing (IV, H) into a separate page that is used for the DMAoperation. Similarly, if the page is in the plaintext read-write state,the VMM encrypts its contents into a separate page used for the DMAoperation. The cloaked page then transitions to the read-only plaintextstate, and is associated with the newly generated (IV, H). Note that inboth plaintext states, the original guest page is still accessible inplaintext form to the application because a transient encrypted copy isused during the actual DMA.

Managing Protection Metadata

Embodiments of the present invention introduce OS-neutral abstractionsfor cloaking both persistent and non-persistent resources, such as filesand private memory regions. In other words, memory mapped data, for bothfile-backed and “anonymous” memory regions, must be managed. For eachresource, protection metadata, such as (IV, H) pairs, must be managed toenforce privacy and integrity, ordering, and freshness (to preventrollback). This management is provided, in embodiments of the presentinvention, by several parts of the described system: the VMM manages theprotection metadata in memory and uses it to encrypt/decrypt and checkthe integrity and ordering of protected data; the cloaked shim manages amapping of “physical resources,” i.e., allocated memory (eitherfile-backed or not) virtual addresses within a given application addressspace, thus permitting a mapping between (IV, H/MAC) pairs and physicalpages to be established for use by the VMM. An unprotected guest OSupdates the cryptographic metadata for protected files as protected dataand protection metadata are both stored in the guest OS. The unprotectedguest OS is only involved in persisting metadata, e.g., storingprotection metadata for on-disk file and an associated on-disk metadatafile.

An overview of the components involved in metadata protection ispresented in FIG. 10. The description to follow begins by examining howmetadata is stored, how protected objects are mapped to metadata, andthen describes how the metadata is used to enforce protection.

Protected Resources

Each cloaked resource, such as a file or an anonymous memory region, isassociated with a unique 64-bit resource identifier (RID) in oneembodiment of the present invention. Each RID has a correspondingresource metadata (RMD) object that stores metadata needed to decrypt,check integrity, and preserve ordering. In one embodiment of the presentinvention, an RMD object is an ordered set of (IV, H) pairs, one perencrypted page, addressed by a 32-bit resource page number (RPN).

An RMD object is an abstraction that serves as a container for theprotection metadata where each resource has a corresponding metadataobject. An RMD object is a logically contiguous addressable object thatmay be created, truncated, extended or deallocated.

An RMD is applied to different types of resources: files; and anonymousmemory regions. In one embodiment of a file-backed RMD, the RID may be alarge integer that uniquely identifies the resource, for example, aninteger corresponding to the <device_id, inode> of a file in the filesystem. In one embodiment, this is a 64-bit value consisting of 32 bitsfor the inode and 32 bits for the device_id. On a local filesystem, itis expected that this is sufficient to allow the RID to uniquelyidentify the file with which it is associated, even in light ofrenaming, etc.

As set forth above, for one embodiment, the RID for a file isconstructed from its device and inode numbers. There is, however, noprotection for file system metadata; consequently, a malicious OS couldswap inputs on an application. In order to provide security for thisfile system metadata, a secure namespace can be provided associatingpathnames with (RID, MAC) pairs. This could be implemented by employinga protected daemon or shared file, which would be updated on fileoperations such as rename, create, and unlink.

When a resource is mapped into memory, its RMD object is loaded into ametadata cache (MDC) 470 in the VMM. A single MDC 470 caches metadatafor all cloaked resources mapped by the guest. This design ensuresmetadata consistency for shared objects, such as files and shared memoryregions.

The MDC is composed of a collection of all RMDs in use by all addressspaces in the system and the MDC can be seen as a collection of objectsindexed by RID.

In one embodiment of the present invention, an entry has the form:[RID->(meta_data, dirty_bit, ref-count), RID->( . . . ), . . . ]

where the dirty_bit indicates if metadata has been modified, and must bewritten out upon eviction from the cache;

where ref-count indicates a number of applications using this resource(it is noted that each application should not indicate more than oncethat it is using a resource;) and

where meta_data is a set of (IV, H/MAC) tuples.

In one embodiment of the present invention, an RMD object is implementedusing a per-RID data structure, which may be referred to as a metadatatranslation table, and which supports a sparse resource address space. Athree-level data structure similar to a page table is indexed by offset(in units of 4K pages).

It can be seen that this three-level data structure implementationsupports a large amount of cloaked file contents. For example, if each<IV, H/MAC> tuple consumes 256 bits (32 bytes), then a single 4K leafpage can store 128 tuples. A single 4K directory page can store pointers(MPNs) for 1K leaf pages. A top-level array of root pages is then usedto index into the directory pages. Each root page can store pointers(MPNs) for 1K directory pages, covering up to 128M tuples, enough for512 GB of cloaked file contents.

Protected Address Spaces

In the x86 architecture, hardware faults and interrupts are generallydelivered through an interrupt descriptor table (IDT). The OS kerneltypically registers a routine for each fault/interrupt type, which isinvoked in kernel-mode when the corresponding fault/interrupt occurs.Traditional hardware delivers hardware interrupts and faults to akernel-mode handler. Typically, user-mode programs must specify handlersfor resolving user-level exceptions through a “signal” deliveryinterface defined and mediated by the OS. Thus, in the x86 architecture,there is no mechanism to invoke a user-mode application handler from theexisting hardware directly, without going through the OS (or guest OS)kernel.

In embodiments of the present invention, the VMM uses cachedvirtual-address mapping information for a cloaked user-mode process orapplication to resolve shadow page table page faults and performcorresponding encryption and decryption operations while running theapplication process in cloaked mode. This VMM-managed software cache isreferred to as a “metadata lookaside buffer” (MLB), analogous to thehardware TLB in modern processors, and will be described below in moredetail.

In embodiments of the present invention, the content of the cloakedvirtual memory of a cloaked process is protected by the VMM usingprotection metadata and associated metadata translations. This dataneeds to be available to the VMM any time the VM is executing in cloakedmode. For example, when a cloaked process touches a page that was notmapped in the shadow page table, the VMM needs to determine whether thepage is cloaked, and if it is cloaked, which protection metadata (e.g.,IV and Hash/MAC) the VMM should use to decrypt and verify the integrityof the page. The VMM can access the metadata translation table and thenlook up the corresponding <IV, H/MAC> from the metadata cache, asdescribed below.

The protection metadata cache in the VMM holds all metadata used by arunning cloaked process, and is thus directly accessible by the VMM.However, the metadata translation table is not directly accessible bythe VMM. Instead, the VMM caches a subset of the metadata translationsin the Metadata Lookaside Buffer MLB. When new entries are inserted intothe MLB table in the user-mode shim, the VMM need not be notified. Onlywhen an entry is needed by the VMM, the VMM makes an “MLB upcall”through the user-level exception mechanism to invoke a handler in theshim.

When the VMM misses in the MLB, however, it needs to invoke a user-mode“MLB miss handler” in the cloaked process to resolve the miss. As above,with the constraints of the x86 architecture, existing hardware cannotinvoke a user-mode handler without the OS kernel.

Embodiments of the present invention provide a control-transfermechanism to perform an “upcall” from the VMM directly to a guestuser-mode handler, without involving the guest OS kernel. As will bedescribed in more detail below, when the VMM experiences an MLB miss,the VMM saves the faulting context and switches contexts to run theshim's MLB miss handler in guest user-mode. Upon completing the handler,the shim returns to the previously-faulted context and continuesexecution. As a result, such faults/upcalls are “invisible” to the OSkernel in that the data or information is never available to the guestOS in cleartext. All other architecturally-defined hardware faults orinterrupts can be delivered to and processed by the guest kernelindependently.

Access control and sharing for cloaked resources are determined by aunique security identifier (SID) that identifies a protection domain orexecution context. In one implementation of the present invention, a SIDis associated with an application instance, which may contain multipleprocesses. Processes with the same SID have common access to cloakedresources. The address space for a cloaked process is identified by aunique address space identifier (ASID) 472, as shown in FIG. 10, thatdefines its shadow context. Portions of multiple cloaked resources aretypically mapped into the guest virtual address space associated with agiven ASID.

The VMM maintains a per-ASID cache of resource mappings in its virtualaddress space, i.e., the metadata lookaside buffer MLB 474. The MLB 474is used to map a virtual address to a resource. An MLB entry has theform (start, end)→(RID, RPN), where start and end denote the virtualaddress range into which the resource is mapped, RID denotes theresource being mapped, and RPN denotes the first RPN in the mapping. Forexample, if file “foo.txt” has RID 4, and its third page (starting from0) is mapped into the first GVPN in the virtual address space, thiswould be modeled as (0,4096)→(4,2).

A shim program 476 is responsible for keeping a complete list ofresource mappings for both cloaked and uncloaked memory and updating theMLB 474 whenever there is a change. The shim 476 resides in the sameguest virtual address space, and interposes on all calls that modify it,such as mmap, munmap, and mremap in Linux. Advantageously, byimplementing these functions in the user-mode shim 476, the VMMimplementation is OS-neutral.

On an MLB miss, the VMM performs an upcall into the shim to obtain therequired mapping, and installs it in the MLB 474, illustrated by themiss action in FIG. 10. The mappings for the shim 476 itself are pinnedin the MLB 474, preventing recursion. Note that if the MLB has anincorrect mapping, it generally fails-closed. If the MLB 474 maps thewrong range of memory for a RID, or if the MLB 474 maps an uncloakedrange as cloaked, then encryption or decryption will fail, or theapplication will end up accessing ciphertext, also causing it to fail.It is believed that failing closed is a better result than continuingoperation on what might be faulty data.

In more detail, referring also to FIG. 6, the VMM first pushes theregisters of the running cloaked process onto the top of an upcallregister stack 604 in a cloaked thread context (CTC) 602 and thenchanges the guest VM's Instruction Pointer (IP), stack pointer (SP) andother general registers 606 with proper arguments to run the “MLBupcall”. The “MLB upcall” handler installs the entry requested by theVMM through hypercalls and then issues a “return-from-upcall” hypercallto return to the VMM. The VMM then pops the registers from the upcallregister stack 604 and resumes cloaked application execution. Note thatrecursive upcalls can be supported up to the memory limit of the “upcallregister stack” in the CTC.

While the user-mode “MLB upcall” handler executes, it may still trapinto the guest kernel through guest page faults, system calls and guesthardware interrupts. From the perspective of the guest kernel, it cannotobserve that the upcall handler is being executed. In fact, the guestkernel cannot observe any code executed in cloaked mode. From theperspective of the application, it would not detect that the handler hasbeen executed either. This is because the execution of the handler isatomic with respect to user-mode application code execution. This isachieved by delaying all signals delivered to the application threadfrom the guest kernel until the upcall returns and the application codeis resumed. The MLB handler would not touch the memory (including shim'sand app's) that would cause the same upcall to be delivered as it wouldresult in an infinite number of upcall deliveries. In this context, theMLB handler would only touch those memory whose VPN->RPN pairs are“pinned” in the VMM's MLB to avoid another upcall to the MLB handler.

In another illustrating example, the application makes a system callthat requires argument marshalling by the shim. If some arguments of thesystem call are pointers to invalid addresses, the kernel typicallyreturns an error code instead of delivering a signal SIGSEGV. Tocorrectly produce the same behavior, the shim needs to touch the invalidguest virtual address to know whether the address is really valid. Ifthe address is truly invalid, the OS would nevertheless deliver SIGSEGV.However, the shim would capture it and rollback any side effect causedby the shim's system call marshalling and deliver the correct syscallerror code to the application.

The “VMM to guest user-mode” upcall mechanism can also be applied to usecases outside the scope of protection of cloaked application data asprovided by embodiments of the present invention described herein. Forexample, traditionally a divide-by-zero exception caused by anapplication is delivered to the kernel. The kernel then delivers asignal to a user-mode handler in the application. With theabove-described user-mode upcall mechanism, the CPU can directly invokethe user-mode handler for divide-by-zero. As another example, anapplication that attempts to dereference a NULL pointer typicallyresults in a page fault generated by the hardware MMU and handled by theOS kernel, which in turn generally delivers a signal to a user-levelhandler in the application. In a virtualized system, the user-modehandler can be directly invoked, without guest OS involvement. User-modeprograms could make use of this feature to implement new programmingalgorithms.

Other VMM-mediated upcall variants are also possible. For example, inanother embodiment of the present invention another upcall mechanism isused to transfer control to the shim when a cloaked application makes asystem call. The system call is intercepted by the VMM and executioncontrol is transferred to a user-mode handler routine registered by theshim. As a result, the system calls made by the application may betransparent to the guest kernel. This control transfer is alsocompletely transparent to the application, as the application does notneed to know that the system call has been intercepted by the shim. Thisallows the application to run under protection of embodiments of thepresent invention without being modified or recompiled.

In embodiments of the present invention, the ability to redirect a trapto guest user-mode code allows for the redirection of system calls tohandlers in the shim without dynamic VMM intervention.

Page Decryption

When a process accesses a cloaked page in its shadow context, its ASIDand GVPN are known. If the page is unencrypted, then the memory accessproceeds normally, without any VMM intervention.

If the page is encrypted, the access will fault into the VMM because theGVPN is not mapped into the shadow for that ASID. The VMM looks up thefaulting address in the MLB 474, and uses the resulting (RID, RPN) pairto index into the MDC 470 and fetch the (IV, H) pair needed to decryptand integrity check the page contents, as represented by the findoperation in FIG. 10. The hash, check, and decrypt steps are performedusing the protocol described previously. If the decryption succeeds,(RID, RPN) pair is invalidated in the MDC 470. The page is then“zapped,” i.e., removed from all shadows, and mapped into the currentshadow for the respective ASID. The original application access requestis then allowed to proceed.

There is, however, one special case. Operating systems commonly zero thecontents of a page before mapping it into userspace, and applicationsdepend on this initialization. If an access is made to a GVPN that isnot mapped in the current shadow, and the (RID, RPN) pair for that pageis not in the MDC 470, then this is construed to be the firstapplication access to the page, and no decryption is necessary. Anembodiment of the present invention checks that the page contents areindeed zero-filled, and assuming this succeeds, the page is simplyzapped and then mapped into the current shadow, and the original memoryaccess is allowed to proceed.

Finally, the VMM stores the (RID, RPN) pair used for each decryptionwith the associated GPPN in the existing VMM pmap structure which storesGPPN-to-MPN translations.

Page Encryption

When the guest kernel (or any context that does not match theapplication SID) accesses a cloaked page, its GPPN is known, but itsASID and GVPN may not be known. The access could originate from anyguest context, e.g., during a virtual DMA operation. If the page isalready encrypted, then the memory access proceeds normally, without anyVMM intervention.

If the page is unencrypted, the access will fault into the VMM becauseit is not mapped in the current shadow. If the page is writable, the VMMgenerates a new random IV; for a read-only page, the existing IV isre-used. The VMM then encrypts the page contents, and computes a securehash H over the encrypted contents. It stores the resulting (IV, H) pairin the MDC 470, at the (RID, RPN) pair previously associated with theGPPN in the pmap during its last decryption. The page is then zapped andmapped into the current shadow, and the original kernel access isallowed to proceed.

Cloning Metadata

The MDC 470 also provides operations to facilitate support for addressspace cloning, such as clone or fork operations in Linux. As an examplefor explanatory purposes only, assume a cloaked process forks a child.Immediately after the fork, the parent and child processes share theirprivate memory regions copy-on-write (COW). In operation, the metadataassociated with all unmodified COW pages remains accessible andsynchronized between the parent and child.

When the fork occurs, each of the parent's private RMD objects is clonedeagerly for the child, by copying all of its existing metadata entries,and assigning it a new RID. This ensures that metadata for any pagesencrypted prior to the fork remain available to the child, even if theparent later modifies them.

In an exemplary situation, meant to aid in explanation but not limit anyclaims appended hereto, suppose the parent causes an encryption of aCOW-shared page after the fork. A subsequent access by the child wouldnot find the metadata required for decryption. One approach is toforcibly encrypt all pages in the parent during the fork, but this couldbe inefficient because few private pages remain encrypted in practice,unless the system is swapping heavily. Another option is to store acomplete backmap for every GPPN, containing all (ASID, GVPN) pairs thatmap it, but this would be complex and resource-intensive.

The solution implemented by one embodiment of the present invention isto mirror the application's process tree in the MDC 470; each RMD objecthas pointers to its parent, first child, and next sibling RMD objects,if any. The MDC 470 also maintains a global 64-bit version number thatis incremented on every RMD creation and page decryption. A version isstored with each RMD object and set to the global version when it iscreated. Similarly, a version is stored along with the (RID, RPN) pairin the pmap for each GPPN and set to the global version each time it isdecrypted. When a page is encrypted, the (IV, H) pair is stored at the(RID, RPN) pair associated with the GPPN, and also recursivelypropagated to any child RMD objects with versions greater than theGPPN's version. Thus, metadata is propagated to all children with pageswhose contents existed prior to the fork, as desired. It should be notedthat when the parent modifies a COW page, it will be encrypted (and itsmetadata propagated to the child) prior to the modification because theguest OS must first read the page to make a private copy for the parentduring the COW fault.

Persisting Metadata

Resources are either persistent or non-persistent. When a resource isnot in use by any process, its respective RMD object is removed from thecache. RMD objects associated with non-persistent memory regions, e.g.,application stack, data, or anonymous shared memory, can be discardedwhen no longer in use. However, RMD objects associated with persistentcontent, such as file-backed memory regions, must generally be saved todisk. In some embodiments, persistent RMD objects are stored as metadatafiles in the guest. Metadata file integrity is protected by a messageauthentication code (MAC), computed using a key derived from the VMM'ssecret key K_(VMM), and stored in the file. One implementation uses HMAC(Hash Message Authentication Code) with SHA-256.

When a process opens a cloaked file, if there is no existing entry inthe MDC 470 for that file's RID, the shim loads the RMD object from itsassociated metadata file, as illustrated by the load action in FIG. 10.Frequently reloading the RMD object or recomputing its MAC might raiseefficiency concerns. The efficiency, however, can be optimized bykeeping RMD objects cached longer in the MDC 470, instead of evictingthem eagerly after they have been committed to disk. Another optionwould be to store MACs in a Merkle hash tree, allowing for moreefficient verification and updates.

As set forth above, each allocated resource has an associated RID thatthe shim uses to refer to the object. The shim attempts to maintain aone-to-one correspondence between the metadata address space of theresource, by RID/offset, and the in-memory data in an applicationaddress space to be able to offer the appropriate virtual to resourceaddress translations for use by the VMM. Advantageously, the shim doesnot need to track (IV, H/MAC) pairs as it manages a per-applicationmapping of VPN to RPN.

To ensure freshness, a 128-bit generation number is also written to themetadata file, and protected by the MAC. The VMM checks this numberagainst a master list of valid generations when the file is loaded. Thisnumber is stored in the MDC 470 as part of the RMD object. Just prior toeviction, it is incremented in both the RMD and master list. The masterlist is stored in the guest, protected by a MAC and its own counterwhich is stored outside of the guest by the VMM.

RMD objects are written to metadata files by a file daemon 478. Thedaemon 478 communicates with the VMM via a hypercall interface, pollingfor metadata that should be evicted from the MDC 470 and persisted todisk. The daemon extracts the metadata for all of its valid RPNs,obtains their respective MAC as generated by the VMM, commits everythingto disk, and finally evicts the RID from the MDC 470; refer to the evictaction in FIG. 10. It should be noted that the daemon 478 is not trustedand all data it handles is protected cryptographically. Advantageously,if the daemon 478 were compromised, only system availability would belost but data privacy and integrity would be maintained.

As above, a main task of the daemon is to provide access to the guestfile system by the VMM. Thus, the VMM may update the contents of theprotection metadata files. The daemon may periodically poll the VMM todetermine if there are any updates that are needed and, if so, thedaemon will read a complete metadata file from the VMM and then writethe data to the file associated with that RID. In one embodiment of thepresent invention, the metadata files are updated when metadata has beenmodified and that file is no longer being used or by virtue of periodicwritebacks implemented to improve system consistency.

Key Management and Access Control

In accordance with the architecture of embodiments of the presentinvention, a range of access control policies is supported, as SIDsprovide a basic primitive for identifying subjects, and RIDs provide abasic primitive for identifying objects. One implementation may startwith a model that assumes mutual trust between all parts of anapplication and dynamically assigns SIDs at startup.

In one implementation, all encryption is performed using a single set ofencryption and MAC keys. It should be noted that key management andaccess control in embodiments of the present invention are orthogonal.The VMM arbitrates who is allowed to access what resources, regardlessof the key with which it was encrypted. Additional keys could be addedto support delegation of administrative tasks, e.g., one key per RIDwould allow different parties to package its own sets of encrypted filesoutside of the VM.

As referenced above, embodiments of the present invention provideseveral abstractions. First, a way of naming objects, by assigning eachcloaked object a unique resource identifier (RID) is provided. Next, amodel of where a given protected object is in memory, using a collectionof objects referred to as a virtual memory area (VMA) is kept. Finally,a record of what cryptographic metadata is associated with a givenobject, e.g., the hash H, and IV previously discussed, is kept in anobject referred to as a resource metadata (RMD) object.

Embodiments of the present invention keep an identifier for eachprotection domain known as a security identifier (SID) and each shadowcontext, i.e., address space, has a corresponding ASID.

OS Integration with Cloaking

The VMM interposes on transitions between the cloaked user-modeapplication and the guest kernel, using distinct shadow page tables foreach. Privilege-mode transitions include asynchronous interrupts,faults, and signals, and system calls issued by the cloaked application.Mediating these interactions in a secure, backwards-compatible mannerrequires adapting the protocols used to interact with the operatingsystem, as well as some system calls. As above, this is facilitated bythe shim program that is loaded into a cloaked application's addressspace on startup.

In the description to follow, the shim is described in the context of aLinux implementation. This approach could be applied to other operatingsystems, e.g., Microsoft Windows, by one of ordinary skill in the artwith an understanding of the description herein. While the system callinterface varies across kernels, low-level mechanisms for system callvectoring, fault handling, and memory sharing, are tied more closely tothe processor architecture than to a particular OS.

Initially, the basic operation of the shim, how it coordinates with theVMM to manage identity, and its interaction with the kernel and VMM toadapt the application for cloaked execution, will be described. Supportfor handling faults, interrupts, and system calls is presented in detailbelow.

Shim Overview

The shim is responsible for managing transitions between the cloakedapplication and the operating system. It uses an explicit hypercallinterface for interacting with the VMM, i.e., a secure communicationmechanism between the guest and the VMM. This arrangement allowsrelatively complex operations, such as OS-specific system call proxying,to be located in user-mode shim code, instead of the VMM. It alsofacilitates extensibility, providing a convenient place to add customfunctionality without modifying the VMM.

Shim Memory

In memory, referring back to FIG. 6, each of the uncloaked shim 610 andthe cloaked shim 600 consists of its own distinct code, data and stackspace. Each application thread has its own shim instance, and allthread-specific data used by the shim is kept in thread-local storage,preventing conflicts between different instances.

The cloaked shim 600 is multi-shadowed like the rest of theapplications. It is responsible for tasks where trust is required tomaintain protection, such as providing well-defined entry and exitpoints for control transfers, and securely moving data between cloakedand uncloaked memory. As shown in FIG. 6, the cloaked shim 600 alsoincludes the cloaked thread context CTC page 602, which is set aside forthe VMM 250 to store sensitive data used for control transfers. The CTCpage 602 includes areas for saving register contents 604, the table ofentry points 606 to shim functions, and a shadow context identity 608for the shadow context containing the shim 600.

The uncloaked shim 610, as represented in FIG. 6, contains buffer space612 that provides a neutral area for the kernel and application toexchange uncloaked data. Trampoline code 614 facilitates transitionsfrom the guest OS to cloaked code. Nothing in the uncloaked shim 610 istrusted or necessary for protection. As a worst case result, theapplication will crash if either the uncloaked shim code or data becomescorrupted and will have to be restarted.

Hypercall Interface

The VMM exports a small hypercall interface to the cloaked shim.Uncloaked code is allowed to invoke operations to initialize a newcloaked context (used to bootstrap). It can also make calls to enter andresume cloaked execution. As control can be transferred only to acloaked context, these calls can be initiated safely by untrusted code.Cloaked code can make hypercalls to cloak new memory regions, unsealexisting cloaked data, and access other useful interfaces, such asmetadata cache operations.

Loading Cloaked Applications

To start a cloaked application, a minimal loader program is run with theshim linked into a distinct portion of its address space. The actualloader is part of the shim; before taking steps to load the program, theshim must bootstrap into a cloaked context.

To create a new shadow context, the shim issues a hypercall with apointer to itself and protection metadata containing hashes for allpages associated with cloaked code and data as described above. The VMMuses this metadata to verify its integrity, as the cloaked shim willhave access to the address space of the cloaked application. Thus, tobootstrap a secure protection domain for the application, the shim mustbe trusted, i.e., not malicious to the application. The call to create anew context also takes a pointer to a portion of thread-local storage inwhich the VMM can setup a new CTC. Once this setup is complete, the VMMtransfers control to start execution in the cloaked shim.

The cloaked shim then runs its loading routine, which reads anexecutable and loadable format (ELF) binary, and maps appropriatesections into memory. When creating anonymous memory regions ormemory-mapping protected files, the shim performs hypercalls to cloaktheir corresponding virtual memory ranges. On a subsequent execve, ifthe target program is cloaked, the loader program is prepended to theexec call so that the new program will also be cloaked.

Identity Management

The VMM needs a reliable procedure for identifying each cloaked processuniquely and precisely in order to locate the resources associated withthe process inside the VMM. Such identification is difficult without theassistance or knowledge of the guest OS, even though the VMM can observeall instructions executed and the contents of all guest registers andmemory.

To switch between shadow page tables, the VMM employs a procedure foridentifying shadow contexts uniquely. Correct identification requiresaccounting for the fact that contexts are associated with guest-levelprocess abstractions, and scheduling is controlled by the OS, not theVMM. For example, the guest kernel may switch contexts while handling afault or system call.

Known approaches for VMM tracking of guest-level processes, such asmonitoring assignments to the current page table root work fairly well,but are not foolproof. Other approaches, such as accessing a guest OSstate at fixed kernel addresses, e.g., the Linux current pointer, is afragile approach, however, as it assumes knowledge of kernel internalsand address space layout, which may differ between OS releases. The VMMcould store identifying information, e.g., a context identifier, at someuser-level fixed virtual address. Unfortunately, this approach isfragile in a situation where the virtual page containing the identifieris not pinned in physical memory as the guest kernel may page it out,and the VMM cannot then page it back in without guest kernelcooperation. Address space layout conflicts and potential aliasingbetween identifier values and data in uncloaked applications presentadditional problems. Still further, these approaches cannot beguaranteed to work in the presence of an adversarial OS.

Embodiments of the present invention use a shim-based technique formanaging identity that does not depend on information about kernelinternals, and does not require the use of pinned memory. As the shimresides within the application virtual address space, its memory ismanaged normally by the kernel, and is reclaimed automatically when theapplication terminates.

The VMM detects when the execution control transfers from the cloakedprocess to the guest kernel, and the VMM saves the original instructionpointer IP and other registers in the context structure. Then the VMMchanges the IP and registers so that the cloaked process resumesexecution from a “self identifying” hypercall. The hypercall thenidentifies the cloaked process to the VMM and the VMM restores theoriginal IP and other registers.

The VMM maintains a separate shadow context for each application addressspace, for which it assigns a unique ASID. Each address space maycontain multiple threads, each with its own distinct CTC. When the shimbegins execution, it makes a hypercall to initialize its CTC. Duringthis initialization, the VMM writes the ASID and a random value into theCTC, and returns the ASID to the caller. The ASID value is notprotected, and can be used by the uncloaked shim. However, since the CTCis cloaked, the random value is protected, and cannot be read by theuncloaked shim.

Shim hypercalls that transition from uncloaked to cloaked execution areself-identifying. The uncloaked shim passes arguments to the VMMcontaining its ASID, and the address of its CTC. The hypercall handlerverifies that the CTC contains the expected random value, and also thatits ASID matches the specified value. Note that the CTC resides inordinary, unpinned application virtual memory. If the hypercall handlerfinds that the GVPN for the CTC is not currently mapped, it returns afailure code to the uncloaked shim, which simply touches the page tofault it back into physical memory, and then retries the hypercall.

Faults and Interrupts

While a cloaked application is executing, OS intervention is required toservice faults or interrupts, such as application page faults andvirtual timer interrupts. FIG. 11 illustrates the flow of control forhandling a fault from a cloaked application, involving the application,its associated shim, the guest kernel, and the VMM. The procedure forhandling a virtual interrupt is essentially identical.

For purposes of explanation, the fault occurs in step 1, and control istransferred to the VMM. In step 2, the VMM saves the contents of allapplication registers to the CTC in the cloaked shim. The VMM then zerosout the application's general-purpose registers to prevent theircontents from being leaked to the OS. Next, the return instructionpointer IP and stack pointer SP registers are modified to point toaddresses in the uncloaked shim, setting up a simple trampoline handlerto which the kernel will return after servicing the fault. Finally, theVMM transfers control to the kernel.

The kernel handles the fault as usual in step 3, and then returns to thetrampoline handler in the uncloaked shim set up in step 2. In step 4,this trampoline handler performs a self-identifying hypercall into theVMM to resume cloaked execution. In step 5, the VMM restores theregisters saved in step 2, and returns control to the faultinginstruction in the cloaked application.

Note that the active shadow page table is switched when transitioningbetween uncloaked and cloaked contexts. Two shadow page table switchesare used to handle a fault in each of steps 2 and 5. The first switch,from the application shadow to the kernel shadow, occurs when the VMMtransitions to the kernel in step 2. The second switch, from the kernelshadow to the application shadow, is performed when the VMM transitionsback to the cloaked application in step 5.

System Call Redirection

The VMM does not manage the shim when it is running in the uncloakedmode as the shim does not need to access the resources maintained by theVMM. The VMM treats the shim in the same manner as any other process. Inembodiments of the present invention, the CTC prevents the guest kernelfrom misrepresenting identity. When a process identifies itself, the VMMverifies the identity by comparing the value located in the CTC againstthe value saved or stored in the VMM for the corresponding process. Onceverified, the cloaked application is able to access existing pagesmapped by the shadow page table that correspond to the process. In otherapplications, if the guest kernel is trusted, the CTC is not needed. Theidentification mechanism, however, can still be used to identifyexecution in the process.

Unlike faults and interrupts, which are intended to be transparent tothe application, system calls represent an explicit interaction betweenthe cloaked application and the kernel. A system call is issued by theapplication using the standard OS calling convention. FIG. 12 depictsthe flow of control for handling a system call from a cloakedapplication, involving the application, its associated shim, the guestkernel, and the VMM. The transitions involved in performing a systemcall are a superset of the transitions presented for handling a fault aspresented in FIG. 11.

The cloaked application performs a system call, step 1, and control istransferred to the VMM. The VMM saves, step 2, the contents of allapplication registers to the CTC in the cloaked shim. The IP is set toan entry point in the cloaked shim corresponding to a system calldispatch handler; similarly, the SP is set to a private stack in thecloaked shim for executing this handler. The VMM then redirects controlto the dispatch handler in the cloaked shim. The cloaked dispatchhandler performs, step 3, any operations required to proxy the systemcall on behalf of the application. For some system calls, this mayinvolve marshalling arguments, copying them to a buffer in the uncloakedshim. The dispatch handler then reissues the system call, substitutingthe marshalled arguments in place of the original application-specifiedvalues. As before, the VMM again intercepts the system call.

Continuing, the VMM saves, step 4, the contents of all applicationregisters in the CTC. Note that the CTC contains two distinct registersave areas: one for the application registers saved previously in step2, and one for the shim registers saved in this step. The VMM thenscrubs the contents of any application registers that are not requiredby the kernel system call interface. The return IP and SP are modifiedto point to addresses in the uncloaked shim, setting up a simpletrampoline handler to which the kernel will return after executing thesystem call. Finally, the VMM transfers control to the kernel.

The kernel executes the system call as usual in step 5, and then returnsto the trampoline handler in the uncloaked shim set up in step 4. Thetrampoline handler performs, step 6, a self-identifying hypercall intothe VMM to enter cloaked execution. In step 7, the VMM restores the shimregisters saved in step 4, and resumes execution in the cloaked dispatchhandler.

The cloaked dispatch handler continues execution, step 8, performing anyoperations required to finish proxying the system call. For some calls,this may involve unmarshalling result values, and copying them intocloaked application memory. The dispatch handler then performs ahypercall into the VMM, requesting resumption of the cloakedapplication. The VMM restores, step 9, the application registers savedin step 2, and returns control to the instruction after the originalsystem call in the application.

As in the case of fault handling, only two transitions require shadowpage table switches between uncloaked and cloaked contexts, i.e., duringsteps 4 and 7.

VMM Access of Guest Virtual Memory

The VMM can generally access the guest's physical memory withoutinvolving either the guest OS or applications. If the VMM needs toaccess the virtual memory of a user-level process and this virtualmemory is not mapped into the physical address space, however, the VMMwill not be able to access it. In one embodiment of the presentinvention, this issue is addressed by providing the hypercall interfacewith the ability to force the guest OS to page in required virtualmemory pages and atomically transition into a mode such that subsequentaccesses from the VMM will succeed.

In an example for purposes of explanation, consider the situation wherethe hypercall protocol for the user-level code in a VM receives an errorindicating that a particular page is not currently mapped in the virtualaddress of the application. Upon receiving the error, the applicationmay access the virtual address to force it to be paged in by the guestOS and then it can retry the hypercall. Multiple retries of thehypercall are possible if multiple virtual pages are needed to be pagedin and the VMM will only process the hypercall if all pages are mappedin the page table. In embodiments of the present invention, thehypercall protocol is only visible to the shim library code, and thus istransparent to the application.

The traditional system call interface between an application and an OSkernel accepts virtual addresses from the application as arguments, andpages in the application memory if it is not currently backed by machinememory. It would only return an error if the virtual address passed infrom the application is not valid.

In a VMM, the VMM can access a guest virtual address if the virtualaddress is mapped to a guest physical address as specified in the guestpage table or cached in the virtual TLB. If the virtual address is notmapped, it will not have access to it. If the virtual address access bythe VMM is for emulating a guest instruction, it would generate avirtual hardware fault and transition the guest execution to the faulthandler.

In embodiments of the present invention, the shim applicationcommunicates with the VMM through this hypercall interface. Somehypercalls pass in memory buffer arguments to the VMM, with the intentthat the VMM will read from the specified memory buffer, and/or write toit. The hypercall that launches the cloaked mode always passes in theCTC as an argument, therefore, as long as the application is executingin the cloaked mode, the CTC is always accessible by the VMM so that theVMM can write the VCPU context to the CTC when a virtual interrupt orfault occurs.

Referring now to the flowchart of FIG. 13, one embodiment of the presentinvention provides a method for assuring that a memory buffer needed bya guest application is currently mapped. In this method, when ahypercall is invoked (step 550) by the application, the VMM handles thehypercall by intercepting (step 552) the hypercall instruction andexamining (step 554) the VCPU registers to determine the hypercallcommand and arguments. If (step 556) one or more of the arguments is avirtual address indicating a location of the memory buffer, the VMMchecks (step 558) whether or not the memory buffer is mapped in theguest page table. Here, an argument may be a pointer, i.e., a virtualaddress, to a parameter in memory, not necessarily a specific memorybuffer, and the VMM reads the contents of that parameter in memory.Further, the VMM knows which arguments are pointers based on thehypercall command, i.e., the VMM does not depend on the particular valuethat is passed. There are several possible ways of checking this, forexample, the VMM may walk the guest's page table to determine whether anapplication virtual address is mapped into guest physical memory. Withhardware support for nested page tables (NPT), e.g., AMD “NPT” (as knownas RVI or Rapid Virtualization Indexing) or Intel “EPT” (Extended PageTables), the hardware may generate a fault if the guest page table doesnot have the page mapped. Alternatively, the VMM may try to access theguest virtual address directly using the shadow page table thatpartially contains guest virtual address mappings to avoid a page walk.In NPT or EPT, such optimization is not possible.

If, at step 558, the VMM finds that the memory buffer is not currentlymapped or it does not have the correct permissions to access the memory,the VMM returns an error and the faulting address (step 560) to thehypercall caller through registers, without actually performing thehypercall. The application receiving the error return value thenattempts to access(step 562) the memory, which causes a page fault to bedelivered to the guest OS. The guest OS resolves the page fault bypaging in the page or changing the permission on the page. For example,if the memory was mapped read-only, such as if the memory iscopy-on-write, and the VMM needs to write to it, the application wouldneed to write to the memory buffer so that the guest kernel would makethe page writeable. Then the application asserts the hypercall to theVMM again (step 550).

Returning now to step 558, if the memory buffer is mapped into a guestpage table then control passes to step 564 where it is determinedwhether or not there are any unexamined virtual address arguments thatremain to be processed. If there are, control passes back to step 554,and if not, then the hypercall is executed, step 566.

If, at step 556, an argument is not a virtual address of the memorybuffer then control passes to step 564 for processing of the hypercall.

It is possible that a memory buffer may span several pages, or severalmemory buffers are needed for the hypercall, as passed in argumentseither explicitly or pointed to, by elements of data structures inanother memory buffer. In such cases, each unmapped page or page withoutthe correct permission would cause the VMM to return an error and thefaulting address. After the application resolves all mapping errors, theVMM proceeds to executing the hypercall.

As an alternate approach, according to one embodiment of the presentinvention, the application may touch each page of a memory bufferimmediately before issuing the hypercall to the VMM. Having theapplication touch each page prior to the hypercall provides someefficiency because doing so may avoid the need to return an error andretry the hypercall. As a virtual interrupt may occur between any twoinstructions in user-level, however, there is no guarantee that thememory buffer would still be mapped when the hypercall instruction isexecuted because the guest OS may have swapped it out before resumingexecution of the application. Thus, although unlikely, it is possiblethat multiple faults may be generated on the same address.

In embodiments of the present invention, the CTC is accessible by theVMM while the application is running in the cloaked mode. There is ahypercall that transitions from the uncloaked to cloaked mode, and inexecuting the hypercall, the VMM makes sure that the CTC is mapped inthe current page table, and the VMM caches the translation in thevirtual TLB. Caching this translation allows the CTC to continue to beaccessible to the VMM as long as the application is running undercloaked mode because, for x86-based systems, the guest cannot flush thevirtual TLB on the VCPU without executing a privileged instruction onthe same VCPU. If this were to happen, the VMM would either interceptthe execution of such a privileged instruction or detect the change tothe TLB as the result of, e.g., a guest TLB flush or invalidationoperation. In either event, the VMM is able to determine whether or nota page is still mapped. On a virtual hardware interrupt or fault, theVMM writes the cloaked register states into the CTC and transitions outof the cloaked mode. As a result, the VMM can have multiple accesses,i.e., continue to access the virtual memory while interleaving with theexecution of other guest programs, which may or may not touch the samevirtual memory. In other words, other programs may execute and suchexecution will not prevent the VMM from accessing the virtual memory ofthe cloaked program.

In yet another embodiment, rather than the VMM monitoring TLBactivities, the VMM could “pin” a page table entry, for example, theCTC, in the VMM for the virtual address it wants to access. This is afurther step because the shadow page table is a cache and, therefore,the translation could be lost, i.e., the translation could be evictedfrom this cache. The loss of the translation could be problematic in asituation where, for example, operation of another VCPU invalidates theunderlying page table entry that maps that virtual address.

Adapting System Calls

Cloaking necessarily changes the way the OS can manage process memory—itcannot modify it or introduce sharing without application help. It alsochanges the way the OS transfers control—it can only branch towell-defined entry and exit points within the application. Accommodatingthese changes requires adapting the semantics of a variety of systemcalls.

Pass-Through and Marshalling

A majority of system calls can be passed through to the OS with nospecial handling. These include calls with scalar arguments that have nointeresting side effects, such as, e.g., getpid, nice, and sync. Theshim need not alter arguments to these system calls, so the cloaked shimis bypassed altogether, resulting in control flow as shown in FIG. 11.Note that the VMM itself is not aware of system call semantics; duringinitialization, the shim indicates which system call numbers can bebypassed.

Many other calls have non-scalar arguments that normally require the OSto read or modify data in the cloaked application's address space, forexample, path names and “struct sockaddrs.” Such arguments aremarshalled into a buffer in the uncloaked shim, and registers aremodified so the system call uses this buffer as the new source (ordestination) for non-scalar data. After the system call completes,results are copied back into the cloaked application, if necessary.

More Complex Examples

Several system calls require changes to resolve incompatibilitiesbetween cloaked semantics and normal OS semantics. There are systemcalls that require non-trivial emulation which, along with threadcreation and signal handling, will be described below.

Emulation

The semantics of several system calls are emulated. For example, thepipe command normally creates a queue in the kernel for communicatingbytes. As this command is not easily protected, it is instead emulatedwith a queue in cloaked shared memory. To preserve the normal blockingsemantics of calls such as read, write, and poll, reads and writes areimplemented over the pipe as normal, however, with a modification. Forthe sender, a write sends zeros instead of actual data. For thereceiver, zeros are read, then actual data is copied from the protectedqueue. Emulation is required to support futex (Linux fast mutex), as thenormal OS implementation involves direct modification of process memory.

For example, sendfile typically takes two descriptors, one for a file,and the other for a socket, and writes the contents of the former to thelatter. This, however, will not work if a file is cloaked in accordancewith teachings of the present invention. Instead, the cloaked file isread first, then its contents are written to the socket using normalsend calls.

Thread Creation

Handling the clone and fork system calls is related to how the shimmanages resources. A “clone” call begins by allocating thread-localstorage for the new thread. Next, the child's cloaked thread context CTCis set up by making a copy of the parent's CTC, and fixing allthread-local pointers for the child. Finally, the IP and SP for enteringcloaked mode in the child's CTC are changed, arranging for the child tostart executing in a “child_start” function located in the child's shim,which will complete its initialization.

Normally, the CTC would be modified by the VMM on a switch from cloakedto uncloaked mode. In this case, however, the child's CTC is notcurrently being used. Thus, on a clone system call, only the parent'sCTC is modified. The uncloaked stack that will be used by the clonedthread, when returning from the system call, is set up so that it willstart running the new cloaked context. After returning from the systemcall, the parent thread returns to the original execution context. Thechild thread begins execution in child_start, as described above.

Signal Handling

Normal Unix signal-handling semantics are incompatible with cloaking, asthe operating system cannot be allowed to transfer control into anarbitrary section of cloaked code. Keeping portions of the shimnon-preemptable also simplifies its implementation.

When the application registers a signal handler with signal, the shimemulates it, registering the handler in its own table. All actual signalhandlers (those registered with the kernel) use a single handler locatedin the uncloaked shim. This signal handler makes a hypercall to the VMMimmediately upon receiving a signal, indicating which shadow contextreceived the signal, the signal that occurred, and any additional signalparameters.

The VMM examines the cloaked context and checks the signal status todetermine in which context the signal occurred: the cloaked shim,uncloaked shim, cloaked application, or other uncloaked code. If thesignal occurred when the cloaked application was executing, the VMMtransfers control to a well-defined signal entry point in the shim, withrelevant signal information. If the signal occurred while the shim wasexecuting, the VMM further checks a flag in the CTC to determine whetherto safely rollback execution to the last application system call entrypoint, or to defer the signal delivery until shim exit, when executionhas effectively returned to the application.

File I/O

Files used by cloaked applications, i.e., cloaked files, are encryptedfrom the view of the guest kernel. As a result, therefore, the kernelfile cache contains only encrypted blocks from these cloaked files. Reador write operations to a partial file block cannot be performed insidethe guest kernel because a partial encrypted block cannot be decryptedwith the exception of using a stream cipher. To provide the level ofsecurity that is provided by embodiments of the present invention,however, it would be very difficult to use a strong stream cipher.

Alternatively, an application may access the same file using read andwrite system calls or through file-backed memory-mapped “mmap regions.”Each mmap region is a contiguous portion of the application's virtualaddress space created via the mmap system call (in Linux) to map memoryfor application use. The synchronization between encrypted and decryptedviews, however, would be expensive if the kernel implements read andwrite system calls using its encrypted view and the application accessesthe file using virtual memory using its decrypted view.

Embodiments of the present invention provide operations for securelyprocessing cloaked file I/O operations—including read and write systemcalls, as well as some inter-process communication (IPC) operations,such as pipes, by emulating the file I/O semantics in the shim layerwith memory-mapped regions using the mmap system call.

Unprotected, i.e., “uncloaked” files, are handled using argumentmarshalling, while protected files must be adapted to utilize cloaking.Each cloaked file has an associated metadata file, as explained above.On an open call, the shim makes a hypercall to determine if the metadatafor its RID is in the VMM's metadata cache MDC. If the metadata is notfound, the shim makes a hypercall to allocate an RMD object in the MDCfor that RID, reads the entire metadata file and passes its contents tothe VMM, which verifies its integrity.

The shim interposes on all I/O-related system calls. Encrypted file I/Ofor cloaked applications is implemented in the shim using mmap. Forexample, read and write system calls are emulated by copying datato/from memory-mapped buffers. File data is mapped using the MMAP_SHAREDflag, to ensure that other processes that may open the same file obtaina consistent view. By transforming all file I/O into memory-mapped I/O,file data is decrypted automatically when it is read by a cloakedapplication, and encrypted automatically when it is flushed to disk bythe kernel. For efficiency, the shim maintains a cache of mapped fileregions; one implementation of the present invention maps regions using1 MB chunks to amortize the cost of the underlying mmap and munmapcalls.

Using mmap for file I/O obviates the need to implement any cryptographyin the shim and allows keys and metadata to be managed, in oneembodiment of the present invention, solely by the VMM. Thisimplementation avoids the need for maintaining consistency betweendifferent views of the same file. Further, with mmap encryption anddecryption need only be performed when necessary. In one non-limitingexample, the application can read portions of a file repeatedly withoutcausing any additional decryptions. This embodiment of the presentinvention provides an advantage over an implementation based on the readoperation, as data would then need to be decrypted each time it waspassed to the application. Similarly, for a write operation, data needonly be encrypted when the OS actually flushes it to disk.

It should be noted that even after a cloaked application terminates,some unencrypted file pages may remain in the OS buffer cache, and canbe used by other cloaked applications from the same SID.

In one embodiment of the present invention, a single-page header isprepended to each cloaked file. This header contains the actual filesize, which may differ from the current on-disk size due to the 1 MBmapping granularity. Each shim using the file maps its header using ashared mmap, to emulate operations such as fstat and lseek. The shimalso tracks operations that create or manipulate file descriptors, suchas dup, and maintains a table of all open files, their offsets, andwhether they are cloaked. This table is kept in a shared anonymousregion to properly track and share descriptors across process forks.

It should be noted that certain files may require special treatment. Forexample, applications need a secure source of randomness forcryptographic purposes, which cannot come from the untrusted OS. This isaddressed by transforming accesses to /dev/random with hypercalls forsecure randomness.

An implementation of a system in accordance with one or more of theembodiments of the present invention described above supports cloakingfor all application memory regions—private and shared, anonymous andfile-backed.

An implementation of an embodiment of the present invention can be basedon a version of the VMware VMM for 32-bit x86 processors that usesbinary translation for guest kernel code. The modified VMM can be builtas a VMware Workstation binary running in a “hosted” configuration ontop of an existing Linux host OS. Of course, as multi-shadowed memorycloaking does not depend on specific features of the VMware VMM,embodiments of the present invention as described herein could also berealized in other virtualization platforms as is apparent to those ofordinary skill in the art.

One of ordinary skill in the art will understand that minormodifications would be necessary to enable hardware-assist for x86virtualization, such as Intel VT and AMD SVM. For example, system calltransitions between guest user-mode and kernel-mode are trapped by abinary-translating VMM, but are not typically trapped by ahardware-assisted VMM. It is envisioned that hardware support for nestedpage tables will accelerate many of the operations, improving overallperformance. Reducing the cost of hardware context switches is alsodesirable. For some embodiments of the present invention, the ability toredirect a trap to guest user-mode code makes it possible to redirectsystem calls to handlers in the shim without dynamic VMM intervention.

Applications

A variety of applications have been run in a system implementingembodiments of the present invention. Cloaking a standard shell likebash or tcsh provides a convenient way to launch other cloakedapplications. Most common commands, e.g., ls, ps, df, rm, have beenimplemented this way as have more complicated console-based tools likemail and traceroute. Shell scripts using simple tools like sed, awk, andgrep have been protected, as have scripts in more complicated languagessuch as Perl and ruby. A variety of web and mail servers have been runwith embodiments of the present invention, including Apache, exim andpostfix.

Embodiments of the present invention are also able to run a variety ofsmall and large applications; from modest programs like xterm andkonsole to larger clients such as Konqueror and Firefox.

Embodiments of the present invention are directed primarily towardsoftware attacks; however, compared to architecture-level approaches,embodiments of the present invention provide substantial flexibility bybeing software-based and do not require applications and/or the OS to besubstantially modified or rewritten. Embodiments of the presentinvention make integration with unmodified operating systems feasible,and enable sharing between protection domains. Nevertheless, embodimentsof the present invention's software mechanisms could be combined withmore hardware-centric approaches to provide similar benefits.

According to embodiments of the present invention as described above, asystem cryptographically isolates an application inside a virtualmachine from the operating system it is running on, offering anotherlayer of protection for application data, even in the face of total OScompromise.

This capability is enabled by multi-shadowing, a novel technique forpresenting different views of “physical” memory in virtualized systems.This allows memory to be cloaked, so that it appears normal to anapplication, but encrypted to the operating system. Cloaking supports aseparation of responsibilities for isolation and resource management,allowing the use of complex commodity operating systems to manageapplication virtual memory and other resources, while relying on asimpler hypervisor to ensure data privacy and integrity.

Design

Embodiments of the present invention target whole-applicationprotection, and the threats that may be directed toward it.

Whole-Application Protection

Embodiments of the present invention implement a system that can bedeployed incrementally, and used for diverse applications. Embodimentsof the present invention protect entire existing applications in situ inexisting commodity operating systems. This approach has severaladvantages:

Ease of adoption. Previous work on protecting applications requiredpartitioning an application into protected and unprotected parts—forcingdevelopers to modify their applications or port to a new OS. Further,changes to how software is packaged and used may also be required byprevious methods.

Support for diverse applications. Solutions for providing higherassurance are often restricted to a limited set of applications or data,such as passwords. Sensitive data, however, is remarkably diverse, fromdatabases of credit card numbers, to files containing medical patientinformation. Sensitive data in real applications frequently does notlend itself to being placed in a separate container, and restructuringapplications is often impractical.

Incremental path to higher assurance. Even after taking the operatingsystem out of the application's trusted computing base, large, complexapplications will still have significant assurance concerns. Refactoringapplications into more-critical and less-critical pieces running inseparate protection domains is ultimately a compelling goal. Embodimentsof the present invention provide an incremental path to achieving this,as cloaking can be used for whole application protection as well asfine-grained compartmentalization.

Threat Model

Embodiments of the present invention prevent the guest operating systemfrom reading or modifying application code, data and registers. Allnon-application access to cloaked data, including DMA from virtual I/Odevices, only reveals the data in encrypted form. Data secrecy,integrity, ordering and freshness are protected up to the strength ofthe cryptography used. If the OS or other hostile code tries to modifyencrypted data, the application will fail-stop.

Most applications are not designed with the expectation that the OS isor becomes hostile. Embodiments of the present invention may be used toimplement a “trusted path” for user interface devices, as this wouldprovide protection for many applications, including web, email, and VOIPclients. In accordance with teachings of the present invention, userinteraction could be protected if the application uses a remote displaysystem that renders to software frame buffers.

Protecting Device Memory.

Many I/O devices present a memory mapped interface to software. For somedevices, embodiments of the present invention can be employed to protectthe contents of “physical” device memory from being inspected ormodified by untrusted software. For example, an interactive VM typicallyprovides a virtual high resolution graphics display that uses amemory-mapped frame buffer. A multi-shadowed frame buffer, in accordancewith one or more embodiments of the present invention could implement atrusted path, by ensuring that a cloaked application's output remainsprivate. This approach can be used to prevent the OS from observing rawdevice memory, and to cloak off-screen display images and other memoryused by window managers and graphics subsystems.

Fine-Grained Cloaking.

Further, in accordance with embodiment s of the present invention.Applications can be modified to apply multi-shadowing selectively, i.e.,cloaking only sensitive pages. For example, two shadow contexts could bedefined for each application: a protected shadow containing cloaked codeand data, and an unprotected shadow for uncloaked code and data. In thismodel, cloaked memory can be accessed only by cloaked code. A shadowcontext would then be identified by the virtual address of the currentinstruction pointer.

In order to interpose on transitions between these shadow contexts, aVMM can change the execute permission of pages in the shadow page tables(independent of guest PTE permissions). In the unprotected shadow, allprotected pages are marked nonexecutable; similarly, in the protectedshadow, all unprotected pages are marked non-executable. When theapplication branches between protected and unprotected code, theresulting permissions based page fault will trap into the VMM, allowingit to switch between shadow page tables.

Additionally, as provided by embodiments of the present invention,control transfers to and from a cloaked application are only permittedat well-defined entry and exit points through mechanisms such as systemcalls and signal delivery. Application registers are also protected fromthe OS, and are securely saved and restored upon entry and exit from anapplication's execution context. Embodiments of the present inventioncan also protect information shared between cloaked applications via thefile system, shared memory, or other forms of IPC.

The embodiments of the present invention may be implemented on one ormore of the VMM products available from VMware of Palo Alto, Calif.Embodiments of the present invention offer an additional layer ofdefense-in-depth. Advantageously, as its protection model is orthogonalto that of the guest OS, protected applications require no additionalprivileges.

Embodiments of the above-described invention may be implemented in allsoftware, all hardware, or a combination of hardware and software,including program code stored in a firmware format to support dedicatedhardware. A software implementation of the above described embodiment(s)may comprise a series of computer instructions either fixed on atangible medium, such as a computer readable media, e.g. diskette,CD-ROM, ROM, or fixed disk or transmittable to a computer system in acarrier wave, via a modem or other interface device. The medium can beeither a tangible medium, including but not limited to optical or analogcommunications lines, or may be implemented with wireless techniques,including but not limited to radio, microwave, infrared or othertransmission techniques. The series of computer instructions whethercontained in a tangible medium or a carrier wave embodies all or part ofthe functionality previously described herein with respect to theinvention. Those skilled in the art will appreciate that such computerinstructions can be written in a number of programming languages for usewith many computer architectures or operating systems and may exist inmachine executable format. It is contemplated that such a computerprogram product may be distributed as a removable media withaccompanying printed or electronic documentation, e.g., shrink wrappedsoftware, preloaded with a computer system, e.g., on system ROM or fixeddisk, or distributed from a server over a network, e.g., the Internet orWorld Wide Web.

Although various exemplary embodiments of the present invention havebeen disclosed, it will be apparent to those skilled in the art thatchanges and modifications can be made which will achieve some of theadvantages of the invention without departing from the general conceptsof the invention. It will be apparent to those reasonably skilled in theart that other components performing the same functions may be suitablysubstituted. Further, the methods of the invention may be achieved ineither all software implementations, using the appropriate processorinstructions, or in hybrid implementations that utilize a combination ofhardware logic and software logic to achieve the same results.

What is claimed is:
 1. In a computer system comprising a virtual machinemonitor (VMM) running on system hardware and supporting a virtualmachine (VM) having a first application and a guest OS running therein,a method of processing file I/O operations for files, the methodcomprising: a first shim program intercepting file I/O calls from thefirst application, the first shim program running completely within thesame VM as the first application and interfacing with the VMM using oneor more hypercalls from the first shim to the VMM; the first shimprogram emulating file I/O semantics of an intercepted file I/O call bymapping a target file to which the intercepted file I/O call wasdirected to a first memory region; and the first application accessing aversion of the target file from the first memory region usingmemory-mapped I/O.
 2. The method of claim 1, wherein the firstapplication is a cloaked application and the target file is a cloakedfile, the method further comprising: the first application accessing anunencrypted version of the target file from the first memory region. 3.The method of claim 2, wherein mapping the target file to the firstmemory region comprises: the first shim program determining if firstmetadata for the target file is cached in the VMM; and if the firstmetadata is not cached in the VMM: the first shim program causing theVMM to allocate a metadata object for the first file; and the first shimprogram passing first metadata, corresponding to the first file, to theVMM.
 4. The method of claim 3, wherein the first application modifiesthe target file, the method further comprising: the VMM generatingmodified first metadata as a function of the modified target file; andthe method further comprising at least one of: the VMM passing themodified first metadata to the shim program; the VMM passing themodified first metadata to an agent process in the guest OS for storage;and the VMM storing the modified first metadata in a location availableto the VMM and outside the guest OS.
 5. The method of claim 3, wherein afirst execution context is associated with the first application, andwherein: only an application associated with the first execution contexthas access to the unencrypted version of the target file through theVMM.
 6. The method of claim 1, wherein the shim program mapping thetarget file to the first memory region comprises: determining if thetarget file is already mapped to a determined memory region; and if itis determined that the target file is already mapped, using thedetermined memory region as the first memory region.
 7. The method ofclaim 6, wherein determining if the target file is already mappedcomprises checking a cache of already-mapped files.
 8. The method ofclaim 1, wherein the intercepted file I/O call corresponds to a systemcall.
 9. In a computer system comprising a virtual machine monitor (VMM)running on system hardware and supporting a virtual machine (VM) havinga first application and a guest OS running therein, a method ofaccessing a first resource that comprises first encrypted resource datacomprising: the first application issuing a first access request foraccess to the first resource; intercepting the first access request suchthat the guest OS does not receive the first access request; mapping thefirst resource to a first memory region; and the first applicationaccessing unencrypted first resource data from the first memory region.10. The method of claim 9, wherein mapping the first resource to thefirst memory region comprises: the VMM determining if first resourcemetadata for the first resource is cached in the VMM; and if the firstresource metadata is not cached in the VMM: the VMM allocating ametadata object for the first resource; and the VMM retrieving the firstresource data from a source external to the guest OS.
 11. The method ofclaim 10, wherein the external source is a file.
 12. The method of claim10, further comprising: the VMM verifying the integrity of the firstresource metadata.
 13. The method of claim 10, wherein the firstresource metadata comprises: metadata to decrypt the encrypted firstresource data; and metadata to verify integrity of the encrypted firstresource data.
 14. The method of claim 10, further comprising at leastone of: the VMM passing the first resource metadata to an agent processin the guest OS.
 15. The method of claim 9, wherein mapping the firstresource to the first memory region comprises: determining if the firstresource is already mapped to a determined memory region; and if it isdetermined that the first resource is already mapped, using thedetermined memory region as the first memory region.
 16. The method ofclaim 15, wherein determining if the first resource is already mappedcomprises checking a cache of already-mapped resources.
 17. The methodof claim 9, wherein the first access request corresponds to a systemcall.
 18. The method of claim 9, further comprising: a first shimprogram to intercept the first access request; and the first shimprogram mapping the first resource to a first memory region.
 19. Themethod of claim 18, wherein mapping the first resource to the firstmemory region comprises: the first shim program determining if firstresource metadata for the first resource is cached in the VMM; and ifthe first resource metadata is not cached in the VMM: the first shimprogram causing the VMM to allocate a metadata object for the firstresource; and the first shim program passing first resource metadata,corresponding to the first resource, to the VMM.
 20. The method of claim19, further comprising: the VMM verifying the integrity of the firstresource metadata.
 21. The method of claim 19, wherein the firstresource metadata comprises: metadata to decrypt the encrypted firstresource data; and metadata to verify integrity of the encrypted firstresource data.
 22. The method of claim 19, wherein the first applicationmodifies the first resource, the method further comprising: the VMMgenerating modified first resource metadata as a function of themodified first resource; and the method further comprising at least oneof: the VMM passing the modified first resource metadata to the shimprogram; the VMM passing the modified first resource metadata to anagent process in the guest OS for storage; and the VMM storing themodified first resource metadata in a location available to the VMM andoutside the guest OS.
 23. The method of claim 19, wherein a firstexecution context is associated with the first application, and wherein:only an application associated with the first execution context hasaccess to the unencrypted first resource data through the VMM.
 24. Themethod of claim 18, wherein the first shim program mapping the firstresource to the first memory region comprises: determining if the firstresource is already mapped to a determined memory region; and if it isdetermined that the first resource is already mapped, using thedetermined memory region as the first memory region.
 25. The method ofclaim 24, wherein determining if the first resource is already mappedcomprises checking a cache of already-mapped resources.
 26. The methodof claim 18, wherein the first access request corresponds to a systemcall.
 27. In a computer system comprising a virtual machine monitor(VMM) running on system hardware and supporting a virtual machine (VM)having a first application and a guest OS running therein, a method ofthe first application accessing a first file, wherein the firstapplication accesses an unencrypted version of the first file, themethod comprising: the first application issuing a first access requestfor access to the first file; intercepting the first access request suchthat the guest OS does not receive the first access request; mapping thefirst file to a first memory region; and the first application accessingthe unencrypted version of the first file from the first memory region.28. The method of claim 27, wherein mapping the first file to the firstmemory region comprises: the VMM determining if first metadata for thefirst file is cached in the VMM; and if the first metadata is not cachedin the VMM: the VMM allocating a metadata object for the first resource;and the VMM retrieving the first resource data from a source external tothe guest OS.
 29. The method of claim 28, wherein the external source isa file.
 30. The method of claim 28, further comprising: the VMMverifying the integrity of the first metadata.
 31. The method of claim28, wherein the first metadata comprises: metadata to decrypt theencrypted first file; metadata to verify integrity of the encryptedfirst file; and first file data.
 32. The method of claim 28, wherein thefirst application modifies the first file, the method furthercomprising: the VMM generating modified first metadata as a function ofthe modified first file; and the method further comprising at least oneof: the VMM passing the modified first metadata to an agent process inthe guest OS for storage; and the VMM storing the modified firstmetadata in a location available to the VMM and outside the guest OS.33. The method of claim 27, further comprising: assigning a uniqueresource identifier to the first file.
 34. The method of claim 27,wherein the VMM mapping the first file to the first memory regioncomprises: determining if the first application is authorized to accessthe unencrypted version of the first file.
 35. The method of claim 27,wherein the first application is associated with a first executioncontext and wherein any other application also associated with the firstexecution context accesses the unencrypted version of the first filefrom the first memory region.
 36. The method of claim 27, wherein theguest OS only accesses an encrypted version of the first file.
 37. Themethod of claim 27, wherein the first access request corresponds to asystem call.
 38. The method of claim 27, further comprising: a firstshim program to intercept the first access request; and the first shimprogram mapping the first resource to a first memory region.
 39. Themethod of claim 38, wherein mapping the first resource to the firstmemory region comprises: the first shim program determining if firstresource metadata for the first resource is cached in the VMM; and ifthe first resource metadata is not cached in the VMM: the first shimprogram causing the VMM to allocate a metadata object for the firstresource; and the first shim program passing first resource metadata,corresponding to the first resource, to the VMM.
 40. The method of claim39, further comprising: the VMM verifying the integrity of the firstresource metadata.
 41. The method of claim 39, wherein the firstresource metadata comprises: metadata to decrypt the encrypted firstresource data; and metadata to verify integrity of the encrypted firstresource data.
 42. The method of claim 39, wherein a first executioncontext is associated with the first application, and wherein: only anapplication associated with the first execution context has access tothe unencrypted version of the first file through the VMM.
 43. Themethod of claim 38, wherein the first shim program mapping the firstresource to the first memory region comprises: determining if the firstresource is already mapped to a determined memory region; and if it isdetermined that the first resource is already mapped, using thedetermined memory region as the first memory region.
 44. The method ofclaim 43, wherein determining if the first resource is already mappedcomprises checking a cache of already-mapped resources.
 45. The methodof claim 38, wherein the first access request corresponds to a systemcall.
 46. In a computer system comprising a virtual machine monitor(VMM) running on system hardware and supporting a virtual machine (VM)having a first application and a guest OS running therein, a method ofaccessing a first resource that comprises first encrypted resource datacomprising: the first application issuing a first access request foraccess to the first resource; a first shim program intercepting thefirst access request, the first shim program running completely withinthe same VM as the first application and interfacing with the VMM usingone or more hypercalls from the first shim program to the VMM; the firstshim program mapping the first resource to a first memory region; andthe first application accessing unencrypted first resource data from thefirst memory region using memory-mapped I/O.
 47. The method of claim 46,further comprising: the first shim program intercepting the first accessrequest such that the guest OS does not receive the first accessrequest.
 48. The method of claim 47, wherein mapping the first resourceto the first memory region comprises: the first shim program determiningif first resource metadata for the first resource is cached in the VMM;and if the first resource metadata is not cached in the VMM: the firstshim program causing the VMM to allocate a metadata object for the firstresource; and the first shim program passing first resource metadata,corresponding to the first resource, to the VMM.
 49. The method of claim48, further comprising: the VMM verifying the integrity of the firstresource metadata.
 50. The method of claim 48, wherein the firstresource metadata comprises: metadata to decrypt the encrypted firstresource data; and metadata to verify integrity of the encrypted firstresource data.
 51. The method of claim 48, wherein the first applicationmodifies the unencrypted first resource data, the method furthercomprising: the VMM generating modified first resource metadata as afunction of the modified unencrypted resource data; and the methodfurther comprising at least one of: the VMM passing the modified firstresource metadata to the shim program; the VMM passing the modifiedfirst resource metadata to an agent process in the guest OS for storage;and the VMM storing the modified first resource metadata in a locationavailable to the VMM and outside the guest OS.
 52. The method of claim48, wherein a first execution context is associated with the firstapplication, and wherein: only an application associated with the firstexecution context has access to the unencrypted first resource datathrough the VMM.
 53. The method of claim 46, wherein the first shimprogram mapping the first resource to the first memory region comprises:determining if the first resource is already mapped to a determinedmemory region; and if it is determined that the first resource isalready mapped, using the determined memory region as the first memoryregion.
 54. The method of claim 53, wherein determining if the firstresource is already mapped comprises checking a cache of already-mappedresources.
 55. The method of claim 46, wherein the first access requestcorresponds to a system call.
 56. In a computer system comprising avirtual machine monitor (VMM) running on system hardware and supportinga virtual machine (VM) having a first application and a guest OS runningtherein, a method of the first application accessing a first file,wherein the first application accesses an unencrypted version of thefirst file, the method comprising: the first application issuing a firstaccess request for access to the first file; a first shim programintercepting the first access request, the first shim program runningcompletely within the same VM as the first application and interfacingwith the VMM using one or more hypercalls from the first shim program tothe VMM; the first shim program mapping the first file to a first memoryregion; and the first application accessing the unencrypted version ofthe first file from the first memory region using memory-mapped I/O. 57.The method of claim 56, wherein mapping the first file to the firstmemory region comprises: the first shim program determining if firstmetadata for the first file is cached in the VMM; and if the firstmetadata is not cached in the VMM: the first shim program causing theVMM to allocate a metadata object for the first file; and the first shimprogram passing first metadata, corresponding to the first file, to theVMM.
 58. The method of claim 57, further comprising: the VMM verifyingthe integrity of the first metadata.
 59. The method of claim 57, whereinthe first metadata comprises: metadata to decrypt the encrypted firstfile; metadata to verify integrity of the encrypted first file; andfirst file data.
 60. The method of claim 57, wherein the firstapplication modifies the first file, the method further comprising: theVMM generating modified first metadata as a function of the modifiedfirst file; and the method further comprising at least one of: the VMMpassing the modified first metadata to the shim program; the VMM passingthe modified first metadata to an agent process in the guest OS forstorage; and the VMM storing the modified first metadata in a locationavailable to the VMM and outside the guest OS.
 61. The method of claim57, wherein a first execution context is associated with the firstapplication, and wherein: only an application associated with the firstexecution context has access to the unencrypted version of the firstfile through the VMM.
 62. The method of claim 56, further comprising:assigning a unique resource identifier to the first file.
 63. The methodof claim 56, wherein the first shim program mapping the first file tothe first memory region comprises: determining if the first applicationis authorized to access the unencrypted version of the first file. 64.The method of claim 56, wherein the first application is associated witha first execution context and wherein any other application alsoassociated with the first execution context accesses the unencryptedversion of the first file from the first memory region.
 65. The methodof claim 56, wherein the guest OS only accesses an encrypted version ofthe first file.
 66. The method of claim 56, wherein the first shimprogram mapping the first file to the first memory region comprises:determining if the first file is already mapped to a determined memoryregion; and if it is determined that the first file is already mapped,using the determined memory region as the first memory region.
 67. Themethod of claim 66, wherein determining if the first file is alreadymapped comprises checking a cache of already-mapped files.
 68. Themethod of claim 56, wherein the first access request corresponds to asystem call.
 69. In a computer system comprising a virtual machinemonitor (VMM) running on system hardware and supporting a virtualmachine (VM) having a first cloaked application and a guest OS runningtherein, a method of processing file I/O operations for cloaked files,the method comprising: a first shim program intercepting cloaked fileI/O calls from the first cloaked application, the first shim programrunning completely within the same VM as the first cloaked applicationand interfacing with the VMM using one or more hypercalls from the firstshim program to the VMM; the first shim program emulating file I/Osemantics of any intercepted cloaked file I/O call by mapping thecloaked file to a first memory region; and the first applicationaccessing an unencrypted version of the cloaked file from the firstmemory region using memory-mapped I/O.
 70. The method of claim 69,wherein mapping the first file to the first memory region comprises: thefirst shim program determining if first metadata for the first file iscached in the VMM; and if the first metadata is not cached in the VMM:the first shim program causing the VMM to allocate a metadata object forthe first file; and the first shim program passing first metadata,corresponding to the first file, to the VMM.
 71. The method of claim 70,wherein the first application modifies the cloaked file, the methodfurther comprising: the VMM generating modified first metadata as afunction of the modified cloaked file; and the method further comprisingat least one of: the VMM passing the modified first metadata to the shimprogram; the VMM passing the modified first metadata to an agent processin the guest OS for storage; and the VMM storing the modified firstmetadata in a location available to the VMM and outside the guest OS.72. The method of claim 70, wherein a first execution context isassociated with the first cloaked application, and wherein: only anapplication associated with the first execution context has access tothe unencrypted version of the cloaked file through the VMM.
 73. Themethod of claim 69, wherein the first shim program mapping the cloakedfile to the first memory region comprises: determining if the cloakedfile is already mapped to a determined memory region; and if it isdetermined that the cloaked file is already mapped, using the determinedmemory region as the first memory region.
 74. The method of claim 73,wherein determining if the cloaked file is already mapped compriseschecking a cache of already-mapped files.
 75. The method of claim 69,wherein the intercepted cloaked file I/O call corresponds to a systemcall.
 76. In a computer system comprising a virtual machine monitor(VMM) running on system hardware and supporting a virtual machine (VM)having a first application and a guest OS running therein, a method ofprocessing file I/O operations for files, the method comprising: a firstshim program intercepting file I/O calls from the first application, thefirst shim program running completely within the same VM as the firstapplication and interfacing with the VMM using one or more hypercallsfrom the first shim program to the VMM; the first shim program emulatingfile I/O semantics of any intercepted file I/O call by mapping a targetfile, to which the intercepted file I/O call was directed, to a firstmemory region; and the first application accessing a version of thetarget file from the first memory region using memory-mapped I/O. 77.The method of claim 76, wherein the first shim program emulating fileI/O semantics comprises: the shim determining access characteristics ofthe target file corresponding to the first application as a function ofa file descriptor received with the intercepted file I/O call.
 78. Themethod of claim 77, wherein determining the target file accesscharacteristics comprises: accessing an entry in a first table as afunction of the received file descriptor, wherein the accessed firsttable entry comprises data characterizing the version of the target fileto which the first application has access.
 79. The method of claim 78,further comprising: accessing an entry in a second table as a functionof the received file descriptor, wherein the accessed second table entryidentifies the first table entry.
 80. The method of claim 79, wherein:each entry of a first plurality of entries in the second tablecorresponds to a different file descriptor; and each entry in the firstplurality of entries points to a same entry in the first table.
 81. Themethod of claim 77, wherein determining the target file accesscharacteristics comprises: accessing an entry in a second table as afunction of the received file descriptor, wherein the accessed secondtable entry identifies a table entry in a first table; and accessing theidentified first table entry, wherein the accessed first table entrycomprises data characterizing the version of the target file to whichthe first application has access, and storing first and second tables inanonymous shared memory-mapped regions.
 82. The method of claim 76,further comprising: mapping the target file to the first memory regionin one or more memory blocks of a predetermined size.
 83. The method ofclaim 82, further comprising: padding the target file with additionaldata such that a size of the padded target file is a multiple of thepredetermined memory block size.
 84. The method of claim 83, furthercomprising: appending a first header to the padded target file, whereinthe first header comprises data indicating an actual size of the targetfile without the additional padding data.
 85. The method of claim 76,wherein the shim program mapping the target file to the first memoryregion comprises: determining if the target file is already mapped to adetermined memory region; and if it is determined that the target fileis already mapped, using the determined memory region as the firstmemory region.
 86. The method of claim 85, wherein determining if thetarget file is already mapped comprises checking a cache ofalready-mapped files.
 87. The method of claim 76, wherein theintercepted file I/O call corresponds to a system call.
 88. In acomputer system comprising a virtual machine monitor (VMM) running onsystem hardware and supporting a virtual machine (VM) having a firstcloaked application and a guest OS running therein, a method ofprocessing I/O operations directed toward a cloaked file, wherein theguest OS only has access to an encrypted view of the cloaked file andthe first cloaked application has access to an unencrypted view of thecloaked file, the method comprising: providing a unique identifier forthe cloaked file; providing a metadata object for the cloaked file in acache in the VMM, wherein the metadata object comprises metadata fordecrypting and verifying integrity of the cloaked file; and providing ashim program to process an I/O call directed toward the cloaked file asa function of the metadata in the metadata object and the uniqueidentifier, wherein the shim program maps the cloaked file to a firstmemory region when the I/O call is received from the first cloakedapplication and the first cloaked application accesses the unencryptedview of the cloaked file at the first memory region.
 89. The method ofclaim 88, wherein the shim program mapping the cloaked file to the firstmemory region comprises: determining if the cloaked file is alreadymapped to a determined memory region; and if it is determined that thecloaked file is already mapped, using the determined memory region asthe first memory region.
 90. The method of claim 89, wherein determiningif the cloaked file is already mapped comprises checking a cache ofalready-mapped files.
 91. The method of claim 88, wherein theintercepted file I/O call corresponds to a system call.